8. Three levels of planning
At 31/10 our site should
Release go live, and we can start
selling!
As a user I want to pay
Iteration with Visa card
8
I don’t
get that #$%@! connection
Daily to VISA working!
7
9. Release planning
• Release
• >> Iteration
• typically 3-6 months
• date-driven or user story-driven
8
10. User story backlog
Sprint 1 Sprint 2 Sprint 3
As a user ... As a user ... As a user ...
8 1 8
As a user ... As a user ... As a user ...
3 8 3
As a user ... As a user ... As a user ...
5 5 8
As a user ...
9
5
11. User story matrix
Fully functional
As a user ... As a user ... As a user ...
8 1 8
Fully featured
As a user ... As a user ... As a user ...
1 5 3
As a user ... As a user ... As a user ...
5 5 8
As a user ...
10
5
12. User story matrix
Fully functional
As a user ... As a user ... As a user ...
8 1 8
Fully featured
As a user ... As a user ... As a user ...
1 5 3
As a user ... As a user ... As a user ...
5 5 8
As a user ...
10
5
13. User story matrix
Fully functional
As a user ... As a user ... As a user ...
8 1 8
Fully featured
As a user ... As a user ... As a user ...
1 5 3
As a user ... As a user ... As a user ...
5 5 8
As a user ...
10
5
14. Release planning
iteration
length?
Release Estimate user
velocity?
Goal stories
prioritise
user stories
11
15. Story points
• Value for size / complexity, without
dimension
• Not directly for effort
• Relative way of estimating (x = 2y)
• Usually with (0), 1, 2, 3, 5, 8, 13, 20, 40, 100
• Start with some stories as baseline
• Create a reference set
12
16. Planning Poker
• After story
explanation, each
team member
picks a card
• 1-2-3 turn cards
• discuss High/Low
• re-iterate
13
17. Sprint Backlog
TO-DO DOING DONE
Concepts
Case
Iteration Plan
14
18. Sprint Backlog
TO-DO DOING DONE
Concepts
Case
Iteration Plan
14
19. Sprint Backlog
TO-DO DOING DONE
Concepts
Case
Iteration Plan
14
20. User Story
As a trainee
I want to poker
Because that sounds ‘fun’
15
21. Thuiszorg App
Lending application
of utilities
•voor borrowers
•voor support
16
22. Thuiszorg App
As system admin
As system admin
I want to register stock
Lending application
I want register lending data
So I can start lending stu of utilities
ff
So I know where what is
•voor borrowers
As system admin s •voor support
As customer
I want to add action product
ucts
I want to see a product overview
So I can m ake unknown prod
So I can borrow what I need
more popular
Als local physician As customer
As customer I want to send ‘receipts’ I want to receive invoices
I want to order on-line So utilities can be paid by the So I can charge my
ave
So that I don’t need to le insurance company insurance company
home
As system admin As system admin As customer
I want to register payment data I want to get reports I want to register once
So I can send invoices So I know status So I can save time later
16
23. Case - Home care
• Create a release plan for our system
• assign a PO
• 3-4 sprints
• Define sprint goals
• Estimate story points in
• Give T-shirt sizes for the rest
17
24. Sprint Backlog
TO-DO DOING DONE
Concepts
Case
Iteration Plan
18
25. Sprint Backlog
TO-DO DOING DONE
Concepts
Case
Iteration Plan
18
26. Sprint Backlog
TO-DO DOING DONE
Concepts
Case
Iteration Plan
18
27. User Story
As a trainee
I want to perform a sprint planning
Because just theory is insufficient to start applying
this in my company
19
28. Sprint Planning
• Product Owner + Team + Experts
• Create Sprint Goal
• For each User Story in this iteration
1. PO clarifies story, team asks questions
2. Team (w/o PO) creates tasks,
(re)estimates size (story or tasks)
20
30. Scrum board
To Do In Process Done
As a user ... As a user ... As a user ...
As a user ... As a user ...
As a user ...
As a user ...
As a user ...
22
31. Sprint Backlog
TO-DO DOING DONE
Concepts
Case
Iteration Plan
23
32. Sprint Backlog
TO-DO DOING DONE
Concepts
Case
Iteration Plan
23
34. Agile Manifesto
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
25
35. 12 principes
Our highest priority is to satisfy the customer
Working software is the primary
1 measure of progress. 7 through early and continuous delivery of
valuable software.
Agile processes promote sustainable
Welcome changing requirements, even late in
development. The sponsors, developers,
2 and users should be able to maintain a 8 development. Agile processes harness change
for the customer's competitive advantage.
constant pace indefinitely.
Continuous attention to technical Deliver working software frequently, from a
3 excellence and good design enhances 9 couple of weeks to a couple of months, with a
agility. preference to the shorter timescale.
Simplicity--the art of maximizing the Business people and developers must work
4 amount of work not done--is essential. 10 together daily throughout the project.
The best architectures, requirements, Build projects around motivated individuals.
5 and designs emerge from self-organizing
teams.
11 Give them the environment and support they
need, and trust them to get the job done.
At regular intervals, the team reflects
The most efficient and effective method of
on how to become more effective, then
6 tunes and adjusts its behavior 12 conveying information to and within a
development team is face-to-face conversation.
accordingly.
26
Notas do Editor
\n
\n
\n
\n
\n
Traditionele projecten\n- milestones zijn Req. rdy, Des. rdy, Coding rdy, Test rdy\n\nAgile projecten\n- milestones zijn Release planning, Iteration Planning, Daily Planning\n
\n
\n
\n
\n
\n
\n
Inspanning komt pas via Velocity in beeld\nVelocity = Story Point / Sprint\nDus met een Velocity van 10, en Sprints van 2 weken en een team van 5 man, weet je dat de Inspanning (op dit moment) 1 dag is per Story Point\n
\n
\n
\n
\n
\n
Eventueel in 2 teams. 1 team met eenvoudige Backlog, tweede team met feature/functional matrix.\nAanpak:\n- benoem PO per team\n- maak aannames over technologie en al beschikbare software\n- ga uit van 3-4 sprints\n\n
\n
\n
\n
Creëer een “sense of focus and abundance” tijdens de sprint planning.\n
Eventueel in 2 groepen: Sprint 1 en Sprint 2\n
\n
\n
Twee mogelijke uitvoeringen:\n- voor mij - wat moet ik met deze cursus starten/stoppen/doorgaan\n- voor de deelnemers - wat gaan zij morgen in hun werk doen\nVoorkeur voor de tweede vorm.\n
Toepassing op planning:\n1\n- ga bij elkaar zitten tijdens release/sprint planning\n- leg uit wat je bedoelt met een requirement\n2\n- voor een sprint van 3 weken kan je veel details wel onthouden, documenteer alleen het noodzakelijke\n- snelle oplevering zorgt ook voor snelle leercurve voor schatten en plannen\n3\n- ga bij elkaar zitten ...\n4\n- elke nieuwe sprint kan iets volledig anders zijn dan vooraf gedacht\n