Presentation by full-stack agile, detailing how to improve the estimating process with Agile. There are many different methods that you can experiment with to find the best that works for you.

1. Ashley-Christian Hardy
Experiment with Estimating

2. Hi, I’m Ashley-Christian Hardy
In Progress…
full- stackagile.com
achardy@fullstackagile.com
@achardypm
facebook.com/ fullstackagile
medium.com/@achardypm
pinterest.com/achardypm
instagram.com/achardypm
linkedin.com/in/achardypm

3. Story Points
3
Story Points – where you measure the complexity of a
user story based on comparison. This method often uses
the Fibonacci sequence and a game called Planning
Poker.

4. Ideal Man Days
Ideal Man Days – this is where you try to estimate based
on an ideal day; with no interruptions and work is
completed efficiently.

5. Task Decomposition
Task Decomposition – this method is where you would
break a user story down into small tasks and try to
estimate each little part of work that needs to be
completed.

6. Parametric Estimate
Parametric Estimating – this uses statistical relationships
between data and other variables, for example estimating volume
by number of lines of code, multiplied by complexity multiplied by
time.

7. 3 Point Estimate
1
3 Point Estimate – this is where you make an estimate based on
previous experience, and come out with 3 outputs: best case
scenario, worst case scenario and probably scenario. These are
combined to give a probability for completion.
2
3

8. Experienced Senior Programmer Days
Experienced Senior Programmer Days – This is where you
estimate what you think an experienced programmer would
estimate, this is similar to ideal man days, only you are estimating
what someone else would estimate.

9. The Experiment

10. Thank you!
Full-stackagile.com
achardy@full-stackagile.com
@achardypm
facebook.com/ fullstackagile
medium.com/@achardypm
pinterest.com/achardypm
instagram.com/achardypm
linkedin.com/in/achardypm
slideshare.net/ ashlychrstn
tumblr.com/ blog/achardypm
https://plus.google.com/ achardypm