5. • Roles
– Product Owner: Owns the product
– Scrum Master: Owns the process
– Team: Owns the software, source-code
6. • Story
– Piece of software relevant to end users
– Functional requirement
– Template
• As an <actor>,
• I wan to <action>,
• So that I can <achievement>.
Story 1: As a community member, I want to have a user profile,
so that I can present myself to the community.
11. • Story Writing Workshop
– Participants
• Product Owner
• Scrum Master
• Team
– Goal
• Populate the product backlog
• Write user stories as far as requirements visibility goes
12. • Story Estimation Workshop
– Participants
• Team
• Scrum Master
– Goal
• Estimate the complexity of stories
– How to run
• Consensus-based technique
• Planning poker
4.27 cm ---{ 5x }--- 21.35 cm
14. • Product Planning
– Product Backlog
Priority Points
Story 1 2
Story 2 3
Story 3 5
Story 4 2
Story 5 2
Story 6 3
Story 7 1
Story 8 2
Story 9 5
Story 10 8
15. • Product Planning
– Product Plan
10 Story 1 2
Epic A Story 2 3
Story 3 5
Story 4 2
8
Story 5 2
33 Product Epic B
Story 6 3
Story 7 1
15
Story 8 2
Epic C Story 9 5
Story 10 8
16. • Sprint Planning
– Sprint Backlog
5
Story 1 2
Sprint 1 Sprint Backlog
Story 2 3
Team Velocity 7
7 points/sprint Story 3 5
Sprint 2
Story 4 2
6 Story 5 2
33 Product
Sprint 3 Story 6 3
Story 7 1
7
Story 8 2
Sprint 4
Story 9 5
8
Sprint 5 Story 10 8
17. • Sprint Planning
– Sprint Plan
Sprint 1 Sprint Complexity Start date End date
Sprint 2 1 5 02 June 15 June
2 7 16 June 29 June
Product Sprint 3
3 5 30 June 13 July
4 7 14 July 27 July
Sprint 4
5 8 28 July 10 August
Sprint 5 5 33 02 June 10 August
10 weeks = 2.5 month project
18. • Release Planning
– Release Backlog
Story 1 2
Story 2 3
High Priority 18 Story 3 5
Release 1 Story 4 2 Release Backlog
Story 5 2
Story 6 3
33 Product
Story 7 1
15 Story 8 2
Release 2 Story 9 5
Story 10 8
19. • Release Planning
– Release Plan
Release Complexity Start date End date
Release 1
Product 1 18 02 June 13 July
Release 2 2 15 14 June 10 June
2 33 02 June 10 August
1) 6 weeks = 1.5 month release
2) 4 weeks = 1.0 month release
20. • Release Planning
– Release Plan (Hidden Complexity)
Release Scenario Buffer (%) Complexity Sprints Release date
1 Unfeasible 0 33 5 10 August
1 Optimistic 10 37 6 24 August
1 Realistic 20 40 7 07 September
1 Pessimistic 30 43 8 21 September
21. • Resulting Planning Tree
5
Story 1 2
Sprint 1
Story 2 3
7
18 Story 3 5
Sprint 2
Release 1
Story 4 2
6 Story 5 2
Sprint 3 Story 6 3
33 Product
Story 7 1
7
Story 8 2
15 Sprint 4
Story 9 5
Release 2 8
Sprint 5 Story 10 8