SCRUM Guide ver 11-2017 Flashcards
Review of the SCRUM Guide to prepare for the PSM Exam on SCRUM.ORG.
When should a Sprint be cancelled?
If it no longer makes sense given the circumstances. BUT, due to the short duration of Sprints, cancellation rarely makes sense.
(The SCRUM Guide Page 10)
What are the attributes of Product Backlog items?
- Description
- Order
- Estimate
- Value
- Test Descriptions that prove “Done”
(The SCRUM Guide Page 15)
What three pillars help the SCRUM Team be effective?
- Optimize flexibility
- Creativity
- Productivity
(The SCRUM Guide Page 6)
What SCRUM Master interaction is demonstrated below (SCRUM Master to Product Owner, SCRUM Master to Dev Team, or SCRUM Master to the Organization)?
Finding techniques for effective Product backlog management?
SCRUM Master to the Product Owner
The SCRUM Guide Page 8
What does Empiricism assert?
Knowledge comes from experience and making decisions based on what is known.
(The SCRUM Guide Page 4)
What is the SCRUM Master’s role in the Sprint Review?
Teaches everyone involved to keep within the time-box.
The SCRUM Guide Page 13
By the end of Sprint Planning the Development Team should be able to explain to whom - how it (the Dev Team) intends to work as a self-organized team to accomplish the Sprint Goal and create the anticipated Increment?
- The Product Owner
- The SCRUM Master
(The SCRUM Guide Page 11)
Who empowers the Development team and what is expected of the Development Team?
The organization - to organize and manage their own work (Being Self-Directed)
(The SCRUM Guide Page 7)
Who is the only person able to cancel the Sprint?
The Product Owner
The SCRUM Guide Page 10
Who is the servant-leader for the SCRUM Team?
The SCRUM Master
The SCRUM Guide Page 7
Why is the Dev Team the only body able to decide the number of items selected from the Product Backlog?
Only the Dev team can assess what it can accomplish over the upcoming Sprint?
(The SCRUM Guide Page 10)
What are these?
- The Product Backlog
- The latest Product Increment.
- Projected capacity of the Dev Team during the Sprint
- Past Performance of the Dev Team
The inputs to Sprint Planning
The SCRUM Guide Page 10
What are the 5 characteristics of a healthy Development SCRUM Team?
- Self-Organizing - turning the Product Backlog items into increments of potentially releasable functionality.
- Cross-Functional - The having all the skills necessary to be self-organizing.
- SCRUM recognizes no titles for the Dev Team members no matter the work being done.
- SCRUM recognizes no sub-teams in the Dev Team.
- Accountability belongs to the Dev team as a whole no matter the individual team members.
(The SCRUM Guide Page 7)
In Sprint Planning who collaborates on understand the work of the Sprint?
The entire SCRUM Team
The SCRUM Guide Page 10
Who does the work within the SCRUM?
The Product Owner may do the work OR have the Development Team do it. However the Product Owner remains accountable.
(The SCRUM Guide Page 6)
What ceremony optimizes team collaboration and performance by inspecting the work since the last event?
The Daily Stand Up
The SCRUM Guide Page 12
SCRUM Teams should posses what two traits?
- Self-organizing
- Cross-Functional
(The SCRUM Guide Page 6)
What limits risk to one calendar month of cost?
A Sprint of one calendar month.
The SCRUM Guide Page 9
What is the recommended unit of deconstructed work?
One day of work or less
The SCRUM Guide Page 11
Who composes the Development part of the SCRUM Team?
The Development team and those the Development Team feels are necessary to deconstruct the work.
(The SCRUM Guide Page 7)
What SCRUM Master interaction is demonstrated below (SCRUM Master to Product Owner, SCRUM Master to Dev Team, or SCRUM Master to the Organization)?
Removing impediments to progress?
SCRUM Master to the Development Team
The SCRUM Guide Page 8
What 5 areas has SCRUM been used extensively worldwide?
- Research and identify viable markets, technologies, and product capabilities.
- Develop products and enhancements
- Release products and enhancements frequently as many times per day.
- Develop and sustain Cloud and other operational environments for product use
- Sustain and renew products
(The SCRUM Guide Page 4)
What happens if a Dev Team has fewer than three individuals?
- Decreases interaction and results in smaller productivity gains.
- May encounter skill constraints during the sprint causing the Dev team to be unable to deliver potentially releasable increments.
(The SCRUM Guide Page 7)
How long should the Sprint Review be?
Four hour for one month Sprints - shorter for shorter Sprints
(The SCRUM Guide Page 13)
Why are Sprints limited to one calendar month for the longest duration?
When a Sprint’s horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase.
(The SCRUM Guide Page 9)
Can the Scope be clarified and re-negotiated between the Product Owner and the Development team during the Sprint?
Yes
The SCRUM Guide Page 9
What SCRUM Master interaction is demonstrated below (SCRUM Master to Product Owner, SCRUM Master to Dev Team, or SCRUM Master to the Organization)?
Understanding product planning in an empirical environment
SCRUM Master to the Product Owner
The SCRUM Guide Page 8
Who decides the number of items selected from the Product Backlog for the Sprint?
The Dev Team
The SCRUM Guide Page 10
How does the Dev team convert the Product Backlog into a working product increment?
By starting to design the system based upon the work needed.
The SCRUM Guide Page 11
How does SCRUM optimize predictability and control risk?
An iterative and incremental approach.
The SCRUM Guide Page 4
When would multiple Product Backlogs be used?
Never Multiple Teams use the same Product Backlog.
The SCRUM Guide Page 15
Who works to forecast the functionality that will be developed during the Sprint?
The Dev Team
The SCRUM Guide Page 10
What is the focus of each Sprint?
Like projects, Sprints are used to accomplish the Sprint Goal of what is to be built, a design and flexible plan that will guide building it, the work and the resultant product increment.
(The SCRUM Guide Page 9)
When is the Sprint Goal Created?
Sprint Planning
The SCRUM Guide Page 11
Sprints enable predictability by what two factors?
- Ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month.
- Limit Risk to once calendar month of cost.
(The SCRUM Guide Page 9)
Who helps those outside the SCRUM Team understand which of their interactions with the SCRUM Team are helpful and which aren’t?
The SCRUM Master
The SCRUM Guide Page 7
Who helps everyone change interactions to maximize the value created by the SCRUM Team?
The SCRUM Master
The SCRUM Guide Page 7
What are the SCRUM events specifically designed to enable?
Critical transparency and inspection.
The SCRUM Guide Page 9
What is considered the essence of SCRUM?
A small team of people. The individual team is highly flexible and adaptive.
(The SCRUM Guide Page 4)
What SCRUM Master interaction is demonstrated below (SCRUM Master to Product Owner, SCRUM Master to Dev Team, or SCRUM Master to the Organization)?
Working with other SCRUM Masters to increase the effectiveness of the application of SCRUM in the organization.
SCRUM Master to the Organization
The SCRUM Guide Page 8
Who ensures that the event takes place and that attendants for Sprint Planning understand its purpose?
The Scrum Master
The SCRUM Guide Page 10
What SCRUM Master interaction is demonstrated below (SCRUM Master to Product Owner, SCRUM Master to Dev Team, or SCRUM Master to the Organization)?
Understanding and practicing agility and facilitating SCRUM events as requesting or needed?
SCRUM Master to the Product Owner
The SCRUM Guide Page 8
What ceremony is described as:
“An opportunity for the SCRUM Team to inspect itself and create a plan for improvement to be enacted during the next Sprint.”?
The Sprint Retrospective
The SCRUM Guide Page 13
What role does the Dev Team have in the Sprint Review?
It discusses what went well during the Sprint, what problems it ran into, and how those problems were solved.
It also demonstrates the work “Done” for acceptance by the PO.
(The SCRUM Guide Page 13)
Who is responsible for promoting and supporting SCRUM as defined in the SCRUM Guides?
The SCRUM Master
The SCRUM Guide Page 7
Each Sprint has a goal of what is to be built a design and flexible plan that will guide building it, the work. What is the result of this process?
The Product Increment
The SCRUM Guide Page 9
When is the Sprint Review held?
At the end of the Sprint
The SCRUM Guide Page 13
Who can force the Development team to work from different sets of requirements from the Product Backlog?
No one!
The SCRUM Guide Page 6
What are the 3 purposes of the Sprint Retrospective?
- Inspect how the last Sprint went well
- Identify and order the major items that went well and potential improvements
- Create a plan for implementing improvements to the way the SCRUM Team does its work.
(The SCRUM Guide Page 14)
Why does the Dev Team Self-Organize?
To undertake the work in the Sprint Backlog, both during Sprint Planning and as needed throughout the Sprint.
(The SCRUM Guide Page 11)
True or False - All events (other than the Sprint) may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process.
True
The SCRUM Guide Page 9
What is a good example of Transparency that has its basis defined as a common standard so observers share a common understanding of what is being seen?
A common definition of “Done”
The SCRUM Guide Page 5
What can be considered a project with no more than a one-month horizon?
The Sprint
The SCRUM Guide Page 9
Why is “Empiricism” important in Agile?
In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision-making.
(The SCRUM Guide Page 16)
Can a committee act as the Product Owner within the SCRUM?
No, the Product Owner is one person, not a committee.
The SCRUM Guide Page 6
Why would a Sprint be cancelled?
If the Sprint Goal becomes obsolete. This might occur if there is a change in direction, or if market or tech conditions change.
(The SCRUM Guide Page 10)