Agile estimation and planning
-
Upload
elad-sofer -
Category
Business
-
view
980 -
download
5
description
Transcript of Agile estimation and planning
![Page 1: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/1.jpg)
Agile estimation and planningElad Sofer -Agile coach.
blog - http://blog.thescrumster.com LinkedIn - http://www.linkedin.com/in/eladsofer
![Page 2: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/2.jpg)
![Page 3: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/3.jpg)
![Page 4: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/4.jpg)
How to estimate this task?
![Page 5: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/5.jpg)
Persistence of time
![Page 6: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/6.jpg)
How long will it take to…
• Read the bible
• Drive to Paris ?
• Solve a math equation ?
• Add support for LDAP ?
![Page 7: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/7.jpg)
![Page 8: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/8.jpg)
Estimate tasks in relative size
• We are not good in measuring absolute values.
• We are good in comparing things.
• We have the basic math skills (or a calculator).
• High accuracy has a high toll.
• Estimates become commitments
• Time is not persistent.
![Page 9: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/9.jpg)
Story points• Name is derived from user stories.• They reflect the “bigness” of a user story.
– How hard it is ?– How risky it is ?– How much of it there is ?
• Relative values matters.• Unitless.• Point values “include uncertainty”.• Easy and quick
– A little effort helps a lot– A lot of effort helps a little more
![Page 10: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/10.jpg)
Estimation techniques• Expert opinion• Analogy• Educated guess• Disaggregating
• Planning poker
![Page 11: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/11.jpg)
Planning poker
1. Each person gets a deck of cards.
2. The item to be estimated is read to all.
3. Attendants ask clarifications for the item.
4. Each person selects a card and puts it on the table facing down.
5. When everyone is done, cards are exposed.
6. If the estimations do not match a short discussion is done. -> Goto 4.
7. Handle next item.
![Page 12: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/12.jpg)
Why planning poker works?
• Those who do the work estimate it.
• Emphasizes relative estimation
• Estimates are within one order of magnitude.
• Reduces anchoring - Everyone's opinion is heard.
![Page 13: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/13.jpg)
Specification length
•One page spec
•Group A
•7 Pages spec
•Group B
173 hours
117 hours
![Page 14: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/14.jpg)
Irrelevant information
•Group A
•added irrelevant details:•End user desktop apps•Usernames & passwords•Etc.
•Group B
39 hours
20 hours
![Page 15: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/15.jpg)
Extra requirements
•Requirements 1-4
•Group A
•Requirements 1-5
•Group B4 hours
4 hours
•Requirements 1-5 but told to estimate 1-4 only
•Group C8 hours
![Page 16: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/16.jpg)
Given anchor
•Group A
•Customer thinks 500 •customer has no technical knowledge•Don’t let the customer influence you
•Group B
555 hours
456 hours
•Same as B customer thinks 50
•Group C99 hours
![Page 17: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/17.jpg)
Why planning poker works?
• Those who do the work estimate it.• Emphasizes relative estimation• Estimates are within one order of
magnitude.• Reduces anchoring - Everyone's opinion
is heard.• Modeled for open discussion – forces
thinking.• It’s quick & fun !
![Page 18: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/18.jpg)
![Page 19: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/19.jpg)
![Page 20: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/20.jpg)
Why traditional planning fails
• Plan is not adaptive.• Focus on activities – Not on features
– Never finish early.– Lateness is passed down.– Dependencies.
• Plan is not priority driven.– Higher risk.– Lower ROI.
• Belief that customers will not change• Estimates become commitments.
![Page 21: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/21.jpg)
What makes planning agile?
• Planning Is not considered as a phase in the project• Focus on business priorities• Deliver something each iteration.• Changes are expected, embrace change.• Plans are easily correctable.• Plan by feature not by activity.• Clear definition of progress
50% = 50% of features complete.
• And…
![Page 22: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/22.jpg)
“It’s better to be roughly right than precisely wrong.”
[John Maynard Keynes[
![Page 23: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/23.jpg)
Product
Portfolio
Strategy
Continuous planning
Daily
Iteration
Release
![Page 24: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/24.jpg)
First, We need a backlog
StoryValueEstimateRisk…
As a user I want to log in securely.
As a user I want to see my balance
As a user I want to see last transactions.
As a manager I want balance report
As a manager I want a report of customer with overdraft.
As a user I want to perform stock operations.
![Page 25: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/25.jpg)
Add value
StoryValueEstimateRisk…
As a user I want to log in securely.
10
As a user I want to see my balance
100
As a user I want to see last transactions.
70
As a manager I want balance report
60
As a manager I want a report of customer with overdraft.
80
As a user I want to perform stock operations.
30
![Page 26: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/26.jpg)
Estimate & asses risk
StoryValueEstimateRisk…
As a user I want to log in securely.
105Low
As a user I want to see my balance
1008Low
As a user I want to see last transactions.
7020Medium
As a manager I want balance report
60BIGMedium
As a manager I want a report of customer with overdraft.
8013Low
As a user I want to perform stock operations.
30BIGHIGH
![Page 27: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/27.jpg)
Prioritization guidelines
![Page 28: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/28.jpg)
Now it is prioritized – We are ready
StoryValueEstimateRisk…
As a user I want to see my balance
1008Low
As a user I want to see last transactions.
7020Medium
As a user I want to perform stock operations.
30BIGHIGH
As a manager I want a report of customer with overdraft.
8013Low
As a manager I want balance report
60BIGMedium
As a user I want to log in securely.
105Low
![Page 29: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/29.jpg)
Sprinting…
• Before the sprint:– The team committed to the following:
• As a user I want to see my balance
• As a user I want to see last transactions.
– Creates the sprint backlog:• They break it down into tasks.• They estimate the time for
each task.
![Page 30: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/30.jpg)
Tracking progress (day 1)
![Page 31: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/31.jpg)
Tracking progress (day 3)
![Page 32: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/32.jpg)
Tracking progress (day 6)
![Page 33: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/33.jpg)
Tracking progress (End)
![Page 34: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/34.jpg)
When the Sprint has finished:
• We now know the current velocity.– Only DONE items count.
• We can now start and “realistically” estimate the expected progress.
![Page 35: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/35.jpg)
Velocity
• How many points can the team(s) complete in one iteration.
• Easy to measure.
• Fixes estimation errors.
• Easily reflects the project status.
• Primary parameter in planning.
![Page 36: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/36.jpg)
How to calculate time?
![Page 37: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/37.jpg)
Burn down charts
• Increase visibility
• Easy to understand.
• Updated automatically & immediately.
• Usually used on release & sprint level.
![Page 38: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/38.jpg)
So what will it be?
![Page 39: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/39.jpg)
![Page 40: Agile estimation and planning](https://reader038.fdocuments.us/reader038/viewer/2022103000/554f48ebb4c905423f8b4b42/html5/thumbnails/40.jpg)
For more information:
Read this
book
And visit my blog