Scrum Flashcards
The Product Backlog is ordered by:
Items are randomly arranged.
Whatever is deemed most appropriate by the Product Owner.
Least valuable items at the top to most valuable at the bottom.
Risk, where safer items are at the top, and riskier items are at the bottom.
Whatever is deemed most appropriate by the Product Owner.
The length of a Sprint should be:
Short enough to keep the business risk acceptable to the Product Owner.
Short enough to be able to synchronize the development work with other business events.
One month or less.
All of the above.
All of the above.
When many Scrum Teams are working on a single product, what best describes the Definition of Done?
It depends.
Each Scrum Team uses its own, but must make their definition clear to all other teams so the differences are known.
All Scrum Teams must have a Definition of Done that makes their combined Increment valuable and useful.
All Scrum Teams must have a Definition of Done that makes their combined Increment valuable and useful.
When does a Developer become the sole owner of an item on the Sprint Backlog?
Never. All Sprint Backlog items are “owned” by the Developers on the Scrum Team.
At the Sprint Planning event.
Whenever a team member can accommodate more work.
During the Daily Scrum.
Never. All Sprint Backlog items are “owned” by the Developers on the Scrum Team.
How much work must the Developers complete for each Product Backlog item they select for a Sprint?
Analysis, design, programming, testing and documentation.
As much as it can fit into the Sprint.
All development work and at least some testing.
Enough so that each Product Backlog item they select meets the Definition of Done.
Enough so that each Product Backlog item they select meets the Definition of Done.
Who is required to attend the Daily Scrum?
The Developers.
The Developers and Product Owner.
The Scrum Team.
The Developers and Scrum Master.
The Scrum Master and Product Owner.
The Developers.
The Developers should not be interrupted during the Sprint and the Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity.
(Which one the following answers is FALSE)
The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint.
The Developers may work with the Product Owner to add or remove work if they find themselves with more or less capacity than expected.
As a decomposition of the selected Product Backlog items, the Sprint Backlog changes and may grow as the work emerges.
The Product Owner can help clarify or optimize the Sprint when asked by the Developers.
The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint.
The Developers should have all the skills needed to:
Complete the project as estimated when the date and cost are committed to the Product Owner.
Do all of the development work, except for specialized testing that requires additional tools and environments.
Turn the Product Backlog items they select into an Increment of useful and valuable product functionality.
Turn the Product Backlog items they select into an Increment of useful and valuable product functionality.
What is the typical size for a Scrum Team?
9.
Minimum of 7.
7 plus or minus 2.
10 or fewer.
10 or fewer.
What are two ways a Scrum Master serves to enable effective Scrum Teams?
By starting and ending the meetings at the proper time.
By facilitating Developer decision-making.
By keeping high value features high in the Product Backlog.
By removing impediments that hinder the Scrum Team.
By facilitating Developer decision-making.
By removing impediments that hinder the Scrum Team.
Which statement best describes the Sprint Review?
It is a demo at the end of the Sprint for everyone in the organization to check on the work done.
It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.
It is a mechanism to control Developer activity during a Sprint.
It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.
The three pillars of empiricism are:
Inspection, Transparency, Adaptation.
Planning, Inspection, Adaptation.
Respect For People, Kaizen, Eliminating Waste.
Planning, Demonstration, Retrospective.
Transparency, Eliminating Waste, Kaizen.
Inspection, Transparency, Adaptation.
Which statement best describes Scrum?
A framework for creating complex products in complex environments.
A complete methodology that defines how to develop software.
A cookbook that defines best practices for software development.
A defined and predictive process that conforms to the principles of Scientific Management
A framework for creating complex products in complex environments.
When does a Sprint conclude?
When the Product Owner decides enough has been delivered to meet the Sprint Goal.
When all Product Backlog items meet their Definition of Done.
When all the tasks are completed by the Developers.
When the Sprint Retrospective is complete.
When the Sprint Retrospective is complete.
Who is responsible for managing the progress of work during a Sprint?
The most junior member of the team.
The Scrum Master.
The Product Owner.
The Developers.
The Developers.
When does the next Sprint begin?
Next Monday.
Immediately after the conclusion of the previous Sprint.
Immediately following the next Sprint Planning.
When the Product Owner is ready.
Immediately after the conclusion of the previous Sprint.
The timebox for the Sprint Planning event is?
8 hours for a monthly Sprint. For shorter Sprints it is usually shorter.
Monthly.
Whenever it is done.
4 hours.
8 hours for a monthly Sprint. For shorter Sprints it is usually shorter.
What is the function or purpose of Management in Scrum?
Continually monitor staffing levels of the Scrum Team.
Identify and remove people that are not working hard enough.
Monitor the progress of the Developers on the Scrum Team.
Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to encourage organizational change that fosters empiricism, self-management, bottom-up intelligence, and intelligent product delivery.
Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to encourage organizational change that fosters empiricism, self-management, bottom-up intelligence, and intelligent product delivery.
