Final Quiz
The type of estimation most commonly used for sprint planning is top-down estimation relative estimation absolute estimation bottom-up estimation
relative estimation
How long does it typically take a team to establish their team's story point Velocity? two months It will change with every sprint 2 sprints 6 months
6 months
The ideal product backlog is A prioritized list of items, of independent value, that the team plans to work on in developing a product that aligns to the product vision A list of requests, defects and changes needed by various users A list of all the tasks needed to complete the work A detailed list of all requirements
A prioritized list of items, of independent value, that the team plans to work on in developing a product that aligns to the product vision
Who is involved in a sprint retrospective session? CHECK ALL THAT APPLY A facilitator The Product Owner Team members end users
A facilitator Team members
The ideal sprint backlog is A detailed list of all requirements A prioritized list of all the tasks needed to complete a particular user story A list of user stories and associated tasks that have been chosen for development based on balancing the Product Owners priorities and the number of story points that can reasonably be accomplished in one sprint. The list of all User Stories in the project, prioritized by the Product Owner to show the order of User Story development.
A list of user stories and associated tasks that have been chosen for development based on balancing the Product Owners priorities and the number of story points that can reasonably be accomplished in one sprint.
Stories are selected for a sprint based on The items that are of highest value to the customer only The number of story points that can be done without going over the team velocity, even if that means getting only a few things done The stories the developers on the team think are important A negotiation between what is of highest value, how many story points will fit into the sprint, and what needs to be done first to support later stories
A negotiation between what is of highest value, how many story points will fit into the sprint, and what needs to be done first to support later stories
The horizontal axis represents [A] in a sprint burndown chart, but [B] in a Release burndown chart
A the days B the sprints
A key difference between Acceptance Test Driven Development and Behavior Driven Development is ATDD requires development of test cases/test scenarios, while BDD does not require documentation BDD is focused on defining requirements in advance and assuring that they are met as defined while ATDD is focused on meeting customer expectations ATDD is focused on defining requirements in advance and assuring that they are met as defined while BDD is focused on meeting customer expectations ATDD is a waterfall approach while BDD is Agile
ATDD is focused on defining requirements in advance and assuring that they are met as defined while BDD is focused on meeting customer expectations
The burndown on your first project sprint shows that the team is not performing up to expectations. By the end of the timeblock, there were user stories still unfinished, even with everyone doing their best. Which of the following is NOT an appropriate adjustment to make? Reduce the velocity for future sprints Lengthen the timeblock slightly for future sprints Ask the team to work overtime in the next sprint Add more resources to the team if possible
Ask the team to work overtime in the next sprint
The purpose of a Sprint Planning meeting includes all of the following EXCEPT Identifying tasks associated with User Stories Validating the amount of expected work in the sprint to avoid overcommitment of resources Getting a commitment from the team to accomplish the work Assigning tasks to individual team members so they know what they need to do throughout the sprint Asking questions and getting clarity on User Stories and acceptance criteria
Assigning tasks to individual team members so they know what they need to do throughout the sprint
In Acceptance Test Driven Development, Test scenarios are started Before coding begins When the coding is done and the software is ready to test In the next sprint You don't need test scenarios in ATDD
Before coding begins
Which type of chart should most likely be used to display development team progress within a sprint? Burndown chart Earned Value chart Burn Up chart Velocity chart
Burndown chart
A new User Story Can only be added to the current sprint if it is high priority Cannot be added to the project without CCB approval Can only be added to future sprints Should be added to the current sprint as soon as it is identified
Can only be added to future sprints
The last thing to be done before starting to close the Agile retrospective is Send a formal report to the Project Sponsor Correct any bugs or problems found with the sprint's deliverables Archive all project documents with the Project Management Office Document action items and assign them to team members for follow-up in the next sprint
Document action items and assign them to team members for follow-up in the next sprint
Columns on the Task Board include all of the following EXCEPT To Do In Process Deferred Completed
Deferred
Even on very large projects, there should be only one team working on one sprint at a time. True False
False
Which of the following is NOT a difference between Exploratory Testing and other testing approaches? Exploratory Testing requires less up-front documentation and planning Exploratory testing emphasizes a creative approach to edge testing Exploratory testing is more chaotic In Exploratory Testing there is less need to document anomalous systems behaviors
In Exploratory Testing there is less need to document anomalous systems behaviors
A key difference between Agile and Waterfall testing is In Agile, there is no need to document test scenarios like you do in waterfall In Agile, testing is always done by a separate QA team In agile, testing is a continuous process, not a phase In Agile, testing is done only at the end of a Release
In agile, testing is a continuous process, not a phase
Planning in an Agile Project Is not done Involves only the Project Manager or Scrum Master Is done at different levels of detail throughout the project is similar to Waterfall planning
Is done at different levels of detail throughout the project
Which is NOT true of the Daily Scrum? Everyone stands up to help keep the meeting short Everyone answers the same three questions It lasts no more than 15 minutes It drives out resolutions to delays or problems with task completion
It drives out resolutions to delays or problems with task completion
Which of the following is FALSE about a backlog grooming session? It is done only at the end of a Release There is at least one in each sprint It is used to re-prioritize remaining user stories It lasts about 30 - 60 minutes
It is done only at the end of a Release
What is the MVP in an Agile Project Minimum Viable Product The Maximum Value Proposition for the customer/client Multiple-use Virtual Platform The Most Valuable Product features
Minimum Viable Product
In which Test Quadrant are you most likely to see non-functional testing as the major focus? Quadrant 3 (e.g. User Acceptance Testing) Quadrant 4 ( e.g. Load Testing) Quadrant 2 (e.g. Story Testing) Quadrant 1 (e.g. Unit testing)
Quadrant 4 ( e.g. Load Testing)
An important difference between Agile retrospectives and Waterfall Post-Implementation Reviews ( Post-mortems ) is retrospectives focus on historical events while post-mortems focus on the current status of the project retrospectives focus on the quality of the code while post-mortems focus on the quality of the team's interactions Retrospectives are for informing the current project, while post-mortems are for informing future projects Post-mortems are for informing the current project, while retrospectives are for informing future projects
Retrospectives are for informing the current project, while post-mortems are for informing future projects
Which of the following is NOT one of the Three Amigos? Tester/QA specialist Scrum Master Product Owner Developer
Scrum Master
Burndown charts are useful for Sprints only -- Use EVM for Releases Releases only -- use burn up charts for sprints reporting to Executive Management only Sprints and Releases
Sprints and Releases
The vertical axis represents __________________ on a burndown chart time effort Cost Story Points
Story Points
What estimation metric tool is often used for sizing the work required to address a story? earned value Story points effort-hours planned cost
Story points
Who is involved in a Waterfall Post-implementation Review (aka Project Post-mortem? ) Team members Stakeholders Scrum Master The Product Sponsor
Team members Stakeholders The Product Sponsor
What is the relationship between the Product Roadmap and the Product Backlog? They are not related The Product Backlog is a general guide to the timeline for implementing themes or areas of functionality while the Product Roadmap is a more detailed set of features They are different terms for the same thing -- it just depends on the specifics of your methodology The Product Roadmap is a general guide to the timeline for implementing themes or areas of functionality while the Product Backlog is a more detailed set of features
The Product Roadmap is a general guide to the timeline for implementing themes or areas of functionality while the Product Backlog is a more detailed set of features
At the end of every sprint The team will demonstrate an initial prototype of progress-to-date. The User Stories in the sprint should be ready to deliver/roll out to the end-user, even if that is not actually done The User Stories in the sprint will always be delivered/rolled out to the end-user The team should be ready to start User Acceptance Testing for a final product
The User Stories in the sprint should be ready to deliver/roll out to the end-user, even if that is not actually done
A difference between Agile and Waterfall Test Plans is The Agile Test Plan addresses only tools and methods, while the Waterfall Test Plan covers resources, scope and test procedures. The Agile Test Plan is written by a separate Test Team or QA group, while the Waterfall Test Plan is written by the Project Manager The Agile Test Plan is done only once throughout the project to set the test strategy, while in Waterfall the Test Plan is re-baselined throughout the project The Waterfall Test Plan might be 20 pages long, while the Agile Test Plan may be about 2 pages.
The Waterfall Test Plan might be 20 pages long, while the Agile Test Plan may be about 2 pages.
Sprint Velocity is The average number of tasks that a team member can accomplish in one sprint The average number of story points that can be accomplished by a Scrum team in one sprint The average number of User Stories that can be accomplished by a Scrum team in one sprint The relative estimation of how long a User Story will take to get to Done
The average number of story points that can be accomplished by a Scrum team in one sprint
Velocity in Agile sprints refers to The number of user stories that can be completed by one team member during the sprint The number of user stories the team can accomplish by the end of the sprint The number of stories completed in a single day The change in how fast the team can deliver user stories across Sprints in a Release
The number of user stories the team can accomplish by the end of the sprint
Which of the following best describes the sprint reflected in this burndown chart? The team got off to a slow start but got caught up near the end of the sprint. The team worked a lot of overtime through most of the sprint The team started out doing work quickly, but lost speed as the sprint progressed The team worked less time at first and had to work overtime near the end of the sprint
The team got off to a slow start but got caught up near the end of the sprint.
Which of the following does not relate to Test Scenarios? They describe a specific user situation or type of user input that needs to be tested Each scenario defines one of several different ways a user might approach a system function They are used to help document the results of testing activities They are created to help assure the completeness of testing activities They don't need to be written down in most Agile testing methods.
They don't need to be written down in most Agile testing methods.
Which of the following are important considerations in Value Thinking when you are prioritizing the items in your Roadmap? (Check all that apply) Things that, if missing, will likely make the end-users/customers dissatisfied with the product Things the client/product owner see as a basic need Things that implement the latest technologies Things the developers want to add to the product Things the end-users/customers don't even know they want yet
Things that, if missing, will likely make the end-users/customers dissatisfied with the product Things the client/product owner see as a basic need Things the end-users/customers don't even know they want yet
What is the purpose of an Agile sprint retrospective? To build consensus and cooperation among the team members To brainstorm user story priorities for the next sprint To reflect on the past in order to improve the process for future sprints in the current project To give the end users an opportunity to provide feedback on what was delivered
To reflect on the past in order to improve the process for future sprints in the current project
Because of the frequent use of retrospectives in Agile sprints, there is no need for a final Post-implementation review at the end of the project, like those done in Waterfall projects. True False
True
Which of the following is NOT a question that should be answered in an Agile Retrospective? Who slowed down team progress during the sprint? What worked well for the team? What did not work well for helping the team successfully complete the sprint? What should we do to improve our process going forward?
Who slowed down team progress during the sprint?
Which of the following is a step in the Project Close process at the end of a project? Document lessons learned all of these Archive any documentation or project artifacts Obtain user/sponsor sign-off
all of these
The Product/Project Roadmap is updated at the end of each sprint never -- it is a team commitment to the customer/Product Owner after approval by the Change Control Board Whenever the scope changes.
at the end of each sprint
Which of the following does NOT describe the Product Owner? Is the key person responsible for setting priorities for features/user stories that the team will work on is a fully committed member of the Scrum Team decides how many story points will be included in a sprint Has the authority to make decisions about the product
decides how many story points will be included in a sprint
Which of the following is NOT and advantage of Agile Testing approaches? Provides developers with earlier feedback eliminates all test documentation requirements Allows greater flexibility Saves time and money
eliminates all test documentation requirements
Regression Testing relates to Quadrant 1 of the Test Quadrant model Is not needed in Agile development ensures that software developed in a previous sprint or release still performs the same way after additional changes have been made Is used to test non-functional requirements
ensures that software developed in a previous sprint or release still performs the same way after additional changes have been made
In the 'generate insights' phase of a retrospective, the team should discuss how to improve the code built in the sprint to make it more effective how to increase team velocity how to improve the way the team processes work feedback on the meeting agenda
how to improve the way the team processes work
Estimating time in hours/days is the primary estimation tool used in scrum for schedule and budget tracking is done at the Story Point level so that appropriate time for tasks can be allocated is done at the task level in Scrum to validate the number of Story Points that are planned. is never done in Scrum
is done at the task level in Scrum to validate the number of Story Points that are planned.
For a typical two-week sprint, a reasonable amount of time for a retrospective session would be about at least 4 hours one to two hours 5 to 15 minutes all day
one to two hours
Sprints typically last ________________ but should be as _____________as possible while still delivering completed units of value two to ve days, short less than two weeks, long One to three months, long two to four weeks, short
two to four weeks, short