3. Scrum projects make
progress in a series of
“sprints”
• Analogous to Extreme
Programming iterations
Typical duration is a calendar
month at most
Product is designed, coded,
and tested during the sprint
www.izenbridge.com 3
Sprint
30 Days
6. Length of the release
Amount of uncertainty
How easy is to get feedbacks
Stability of priorities
The overhead of iterating
Give a feeling of urgency
www.izenbridge.com 6
14. Only when sprint goal become completely
invalid
Product Owner has the authority to cancel
the sprint
Very Uncommon
When terminated
◦ Scrum team perform a sprint
retrospective.
◦ Plan the next sprint, with a different goal
www.izenbridge.com 14
15. Sprints are the skeleton of the Scrum framework
Sprints are timeboxed
Sprints should be consistent in length
No goal-altering changes in scope are permitted
During each sprint, a potentially shippable
product increment is completed
www.izenbridge.com 15
18. A. Establishes a WIP Limit
B. Forces Prioritization
C. Demonstrates Progress
D. Helps in controlling
technical debts
www.iZenBridge.com 18
19. A. Daily Scrum
B. Sprint Review
C. Release Planning
D. Sprint Planning
www.iZenBridge.com 19
20. A. Increase the sprint length for
remaining duration of the
project
B. Increase the sprint length for
some upcoming iterations
C. Retrospect on reasons and
identify root cause of this
problem
D. Extend the length of the
sprint on case to case basis
www.iZenBridge.com 20
21. A. Sprint Backlog
B. Product Backlog
C. Sprint Goal
D. Project Vision
www.iZenBridge.com 21
22. A. Quality Checklist
B. Quality Matrices
C. Definition of Done
D. Definition of Ready
www.iZenBridge.com 22
23. This Presentation includes extract from Mike Cohn’s
Presentation www.mountaingoatsoftware.com
Includes Reference from Scrum Guide (www.scrum.org)
This Presentation includes extract from Mike Cohn’s
Presentation www.mountaingoatsoftware.com
Includes Reference from Scrum Guide (www.scrum.org)
www.izenbridge.com 23