Scrum Events Flashcards
g
What are the four Scrum Events?
- Daily Standup
- Sprint Planning
- Sprint Review
- Sprint Retrospective
What are the key elements of Sprint Planning
- Process of selecting PBIs for next sprint.
- Transform the Product Backlog into an actionable plan for a product increment.
What are the Sprint Planning Meeting Inputs
- Ordered product backlog
- Record of completed BPIs from previous product increments
- Knowledge of past performance of team
- Dev team capacity
What are the Sprint Planning Meeting Outputs?
- Sprint Backlog
- Sprint Goal
- Sprint Plan
What is Backlog Refinement?
Goal is to ensure BPIs are well-defined, prioritized & ready for inclusion in upcoming Sprints.
- Can happen anytime
- Improvements and adjustments to BPI’s based upon on new or changed information.
- Progressive elaboration
- Team collaboration
What is the Daily Scrum and what are the organizational rules?
- Max 15 minutes a day.
- Every day - same time and (if on-site) location.
- Scrum alliance says entire team attends
- Only Devs speak
What is the result of the Sprint Review? Select one answer.
a) A list of improvements that the Scrum Team will implement in the next Sprint
b) A revised Product Backlog that defines the probable Product Backlog items for the next Sprint
c) Common understanding of what can be delivered in the Increment and how will the work needed to deliver the Increment be achieved
d) Common understanding of progress toward the Sprint Goal and how progress is trending toward completing the work in the Sprint Backlog
b
What is the time-box for the Sprint Review? The sprint is assumed to be 4 weeks long.
a) 3 hours
b) 4 hours
c) It depends on how much work was done in the previous sprint
d) 2 hours
4 hours
b
4 hours
Product Backlog Refinement practice focuses on items for upcoming Sprints, not the current Sprint.
True
False
False
During the Sprint, the Sprint Goal can be changed?
True
False
False
During the Sprint, if new work is required, the Developers can add it to the current Sprint Backlog.
True
False
True
Who must ensure the new increment meets the Definition of Done?
1. Scrum Master
2. Product Owner
3. Developers
4. Scrum Team
5. QA Specialists
3
How much of the Sprint Backlog must be defined during the sprint Planning meeting?
1. Just enough to understand design & architectural implications
2. Entire Sprint Backlog must be identified and estimated by the end of the Sprint Planning meeting
3. Enough so the Developers can create their best forecast of work they can complete, and to start the first several days of the Sprint
4. Just enough tasks for the Scrum Master to be confident in the Developer’s understanding of the Sprint
3
A Sprint could be cancelled if the Sprint Goal becomes obsolete.
True
False
True
Multiple Scrum Teams working on the same project must have the same Sprint start date
True
False
False
Who is allowed to change the Sprint Backlog during the Sprint?
1. Developers
2. Devs & PO
3. Scrum Team
4. PO
5. Scrum Master
1
What topics should be discussed at the Sprint Review?
1. Coding & engineering practices
2. Sprint results
3. The Scrum process and how it was used during the Sprint
4. All of the above
2
When does the Sprint end?
1. Immediatelly after the Sprint Review
2. When the time-box expires
3. When there is no work remaining in the Sprint Backlog
4. It depends upon the Product Owner
2
What are the properties of the Daily Scrum? (2 answers)
1. Scrum Master asking team members the 3 questions
2. Facilitated by the Team Lead
3. 15 minutes in duration
4. Location & time should remain constant
5. Held first thing in the morning
6. It is free-form & designed to promote conversation
3 & 4
Multiple Sprint Teams working on the same must have the same Sprint start date.
True
False
False
What is the outcome of the Sprint Review?
1. A new increment ready to be released.
2. A revised Sprint Goal
3. A revised Product Backlog
4. A revised Definition of Done
5. A revised Sprint Backlog
3
Which of the following statements are true? Select all that apply
1. After the Sprint Planning, a Sprint cannot proceed without a Sprint Goal.
2. After the Sprint Planning, a Sprint cannot proceed without a complete requirements specification
3. After the Sprint Planning, a Sprint cannot proceed without a complete Sprint Backlog
4. After the Sprint Planning, a Sprint cannot proceed without a complete architecture
1 & 3
When does a Sprint end?
1. Immediately after the conclusion of the Sprint Review
2. When the time-box expires
3. It depends on the PO.
4. When there is no work remaining in the Sprint Backlog
2
An increment can only be delivered to stakeholders at the Sprint Review.
* True
* False
False
An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable.
Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.