Agile Planning and Estimating
Agile Planning and Estimating
Agile Planning and Estimating
WEBINAR
2018
Agenda
• Why plan?
• What is an agile plan?
5
One way of estimating of user stories: Planning Poker!
Planning Poker
• Each estimator is given a denk of cards
• Customer / Product Owner introduces a story/ feature and it’s discussed briefly
2. Read a densely written 5-page research paper about the people influencing
forces within a scrum implementation in an academic journal.
3. Write the product backlog for a simple eCommerce site that sells only NFC
chips.
4. Recruit, interview, and hire a new team member for your squad.
exercise @ planningpoker.com
Why planning poker works?
• Those who will do the work, estimates the work.
• Estimators are required to justify estimates.
• Discussion on common ground, not on specific expertise.
• Combining individual estimates through group discussion leads to better
estimates.
• Relative rather than absolute estimating (faster).
• Everyone’s opion is heard.
• It’s fun! “Planning poker estimation is a means, not the goal”
T-Shirt sizing
• Also a “relative” estimation technique
• Prevents over-analyzing (risk with points)
• Often used on epic or theme level (very big stories)
• Often used to quickly estimate a complete backlog
PLANNING
(BOTTUM-UP)
Daily planning (the scrum or stand-up)
• Examine plan on task/story level
• What will we “as a team” do the upcoming 24 hours.
• Step 1: Gain insight, where are we standing towards our sprint goal and
stories
e.g. What did i do last 24 hours .... What will i do upcoming 24 hours ... Am I hampered ...
200/20 =
200 points Velocity = 20
10 iterations
velocity is simply a measure of
how fast a specific team is going
Step 4. Divide the work into portions per release or per sprint
Keep in mind!
you don’t know everything yet,
keep some ‘slack in your sprint’
Some related metrics & measures
QUESTIONS?