This session was by Tejaswini M, Agile coach,
techniques and best practices of user story estimation & a practical session on How to Write good user stories, Acceptance Criteria and estimating the Stories using different techniques.
2. What do we consider
while doing an
estimation?
While estimating, do
we need to know who
will be working on
that part of the
delivery?
Who does the
estimate?
Does it really matter –
if you are putting
more effort while
doing the actual
work?
Does estimating in
hours mean we know
what our pace of work
should be to ensure
completion on time?
3. Agenda
Quick Overview of Estimates
Experiencing estimation through activities
Different EstimationTechniques
7. What are the parameters for estimation?
Risk Effort ComplexityFunctionality
Current
Knowledge
8. How do we do
Estimation?
• Ideal Days
• Story Points
9. Ideal Time
How long something will
take if:
• It’s all you work on
• No one interrupts you
• And everything you
need is available
Ideally
• Monday has 8 hours
• Every week has 40
hours
But instead
Each day we have
• 2 hrs of meeting
• 1 hr of emails
• 1 hr of status reporting
• 3 hrs left for the project work only
10. How Tall are these Buildings?
Relative v/s Absolute
The Great Pyramid The Eiffel Tower Petronas Towers Burj Khalifa
139.5m
324m
452m
828m
11. Story Points
• Story Points are the unit of
measurement for expressing the
overall size of a user story, feature,
or the piece of work.
• The number of story points
associated with a story represents
the overall size of the story.
• Either doubles OR Fibonacci Series
• Fibonacci Series [1,2,3,5, and 8]
• Doubles [1,2,4, and 8]
1 2 3
5 8 13
20 40 100
15. How Planning Poker Works
An iterative approach to estimating
Steps:
• Each estimator is given a deck of
cards, each card has a valid estimate
written on it
• Customer/product owner reads a story
and it’s discussed briefly
• Each estimator selects a card that’s his
or her estimate
• Cards are turned over so all can see
them
• Discuss difference (especially outliers)
• Re-estimate until estimates converge
Image source: www.iag.biz/resource/scrum-playing-planning-poker/
Delivery Forecasting - estimate helps to understand the delivery forecast as to how long will it take to do the project
From agile perspective estimation gives us a scope to come to a concurrence on sprint commitment
Person dependency - Promotes Pull and encourages to become true cross functional in long term
What part of estimation?
Inaccurate by defination
It can never be accurate as there are always runtime uncertainities
Value of estimation in agile world – better business plan
Teams commitement
Building trust
Overcoming fear of failure
Safe environment to fail
How long Something would take if
It’s all you worked on
You had no interruptions
And everything you need is available
Factors affecting Ideal Time:Training, Email, Reviews, Interviewing, Demonstrations, Meetings, Sick Time, Phone, Bug Fixing, Management review
Relative estimates- human brain is mapped in such a way that he is good at comparision rite
Focuses manily on the Size and the complexity
Absolute- when you are trying to be accurate there is lot of chances of going wrong
Absolute estimates-focus mainly on the ideal time