Scrum Flashcards
When was SM invented?
Early 90’s
When was the SG written?
2010
Who created SM?
Jeff Sutherland & Ken Schwaber
What is the definition of SM?
Helps people, teams and orgs to generate value through adaptive solutions for complex problems.
What is STheory?
- Empiricism and lean thinking
- Optimizes predictability and risk control.
What are 3 pillars of STheory?
- Transparency
- Inspection
- Adaptation
What is transparency?
The process and work must be visible to those performing and receiving the work.
What are consequences of low transparency?
Decision that diminish value and increase risk.
What does transparency enable?
Inspection. Inspection without transparency is misleading and wasteful.
What is a bottleneck to adaption?
Unempowered and non self-managing individuals.
What are the 5 SM Values?
- Focus
- Openness
- Respect
- Commitment
- Courage
Who are the 3 players of SM?
- Scrum Master
- Product Owner
- Developers
What does a SM do?
Enforce the SG through removing impediments, coaching and events are kept within the timebox.
Who manages stakeholder collaboration?
Scrum Master
Who helps ST understand the need for clear and concise PB?
Scrum Master
What is the Product Owner responsible for?
Creating Product Backlog items and ensuring it is visible and understood.
What are Developers responsible for?
Creating a plan for the Sprint or Sprint Backlog, adhering to the Definition of Done and adapting their plan.
How many people should be in a Scrum Team?
10 or fewer.
What is a Scrum Event?
Formal opportunity to inspect and adapt artifacts.
How long should a Sprint be?
1 month or less.
When does a new Sprint start?
Right after the conclusion of a previous one.
What happens during a Sprint?
The Product Backlog is refined as needed.
What happens when a Sprint is too long?
Could become too complex and risk can arise.
When can Sprints be cancelled?
If the Sprint Goal becomes obsolete.
Who has the authority to cancel the Sprint?
The Product Owner.
What is the purpose of Sprint Planning?
To lay out the work to be performed for the Sprint.
Who is the Sprint Planning created by?
Entire Scrum Team.
Who can come to the Sprint Planning?
The Scrum team and invited outsiders to provide advice.
What questions should be asked during Sprint Planning?
- Why is this Sprint valuable?
- What can be done in this Sprint?
- How will the chosen work get done?
What is the timebox of Sprint Planning?
A maximum of 8 hours for a 1 month Sprint.
How long should a Daily Scrum be?
15 minutes.
When do non-Developers participate as Developers?
If the Product Owner or Scrum Master are actively working on items in the Scrum Backlog.
What is the purpose of a Scrum Review?
Inspection of the outcome of the Sprint and determine future adaptions.
What is the timebox of a Scrum Review?
Maximum of 4 hours for a 1 month Sprint.
What is the purpose of a Sprint Retrospective?
Plan ways to increase quality and effectiveness for the next Sprint by evaluating the previous Sprint.
What is a Sprint Artifact?
Represents work or value
What is a Product Backlog?
Ordered list of what is needed to improve the product
What is a Product Goal?
Describes a future state of the product which can serve as a target for the Scrum Team to plan against.
What items does a Sprint Backlog consist of?
- Sprint Goal (Why)
- Set of Product Backlog Items selected for the Sprint (What)
- Actionable plan for delivering the Increment (How)
How much detail should be in a Sprint Backlog?
Enough for Developers to inspect their progress in the Daily Scrum.
What is the Sprint Goal?
Single objective for the Sprint.
When is a Sprint Goal created?
During the Sprint Planning.
Where can the Sprint Goal be found?
In the Sprint Backlog.
What is an Increment?
A stepping stone towards the Product Goal.
What is Definition of Done?
State of the increment when it meets quality measures required for the product.
When does a Product Backlog become an Increment?
When a Product Backlog meets the Definition of Done it becomes an Increment.
What happens if a Product Backlog does not meet the Definition of Done?
It is not presented in the Scrum Review and returns to the Product Backlog for future consideration.