This document provides an overview of estimating and planning in Agile projects. It discusses concepts like sprint backlogs, user stories, planning poker, and different levels of planning from releases down to daily planning. Examples of user stories, story points, and planning techniques are provided. The document also discusses Agile principles like self-organizing teams, frequent delivery of working software, and the value of individuals and interactions over processes.

1. Agile Intro
Module 3
Estimating & Planning
1

2. Sprint Backlog
TO-DO IN WORK DONE
Concepts
Case
Iteration Plan
2

3. Sprint Backlog
TO-DO IN WORK DONE
Concepts
Case
Iteration Plan
3

4. User Story
Als een cursist
Wil ik weten hoe planning in Agile projecten
verloopt
Omdat we zonder planning niet weten wat we
moeten doen en niet weten hoe ver we zijn
4

5. Agile versus Plan-driven
• Agile tegengesteld aan plan-driven?
• Geen BPUF ! Maar heel veel planning.
5

6. Zes niveaus van planning
strategy
portfolio
product
release
iteration
day
6

7. Cone of Uncertainty
grove,
onnauwkeurige
schatting
preciese
schatting
7

8. Drie niveaus van
planning
Op 31/10 moet de site live
Release en gaat we onze applicatie
verkopen
As a user I want to pay
Iteration with Visa card
8
Ik krijg die #$%@!
Daily verbinding naar VISA niet aan
de praat
8

9. Release planning
• Release
• >> Iteration
• typically 3-6 months
• date-driven or user story-driven
9

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 ...
10
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 ...
11
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 ...
11
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 ...
11
5

14. Release planning
iteration
length?
Release Estimate user
velocity?
Goal stories
prioritise
user stories
12

15. Story points
• Waarde voor grootte / complexiteit,
zonder dimensie
• NIET voor inspanning / effort
• Relatieve manier van schatten (x = 2y)
• Meestal met (0), 1, 2, 3, 5, 8, 13, 20, 40, 100
• Start met enkele stories als baseline
• Bouw een referentie-set op
13

16. Planning Poker
• After story
explanation, each
team member
picks a card
• 1-2-3 turn cards
• discuss High/Low
• re-iterate
14

17. Sprint Backlog
TO-DO IN WORK DONE
Concepts
Case
Iteration Plan
15

18. Sprint Backlog
TO-DO IN WORK DONE
Concepts
Case
Iteration Plan
16

19. Sprint Backlog
TO-DO IN WORK DONE
Concepts
Case
Iteration Plan
17

20. User Story
Als een cursist
Wil ik wel eens pokeren
Omdat dat wel ‘fun’ klinkt
18

21. Thuiszorg App
Uitleenadministratie
van hulpmiddelen
•voor leners
•voor beheerders
19

22. Thuiszorg App
Als beheerder
Als beheerder n Uitleenadministratie
Wil ik uitleengegevens vastleggen Wil ik voorraad invoere
wordt
Zodat ik weet wat waar is Zodat uitlenen mogelijk van hulpmiddelen
•voor leners
en •
Als beheerder voor beheerders
Als klant
Wil ik reclame akties invoer
en
Wil ik een productoverzicht zien
Zodat ik o nbekende product
Zodat ik kan kiezen wat mij past en
bete r bekend kan mak
Als huisarts
Als klant
Als klant Wil ik ‘recepten’ kunnen doorgeven
Wil ik een factuur krijgen
Wil ik on-line bestellen Zodat producten door de
Voor de verzekering
kel hoef
Z odat ik niet naar de win verzekering betaald worden
Als beheerder Als beheerder Als klant
Wil ik uitleengegevens vastleggen Wil ik overzichten krijgen Wil ik eenmalig registreren
Zodat ik weet wat waar is Zodat ik de status weet Zodat ik tijd spaar
19

23. Case - iPhone app
• Stel een release planning op voor onze App
• benoem PO
• 3-4 sprints
• Definieer sprint goals
• Schat story points in (voor de eerste 3-5)
• Geef T-shirt maten voor de rest
20

24. Sprint Backlog
TO-DO IN WORK DONE
Concepts
Case
Iteration Plan
21

25. Sprint Backlog
TO-DO IN WORK DONE
Concepts
Case
Iteration Plan
22

26. Sprint Backlog
TO-DO IN WORK DONE
Concepts
Case
Iteration Plan
23

27. User Story
Als een cursist
Wil ik wel eens een Sprint Planning uitvoeren
Omdat alleen theorie onvoldoende is om dit in
onze organisatie toe te passen
24

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)
25

29. Let’s practice ...
• Voer een Sprint planning meeting uit
26

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 ...
27

31. Sprint Backlog
TO-DO IN WORK DONE
Concepts
Case
Iteration Plan
28

32. Sprint Backlog
TO-DO IN WORK DONE
Concepts
Case
Iteration Plan
29

33. Retrospective
Start doing
Stop doing
Continue doing
30

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.
31

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.
32