full-stack agile: Experiment with Estimating

Post on 19-Feb-2017

787 views 0 download

Transcript of full-stack agile: Experiment with Estimating

Ashley-Christian Hardy

Experiment with Estimating

3

2 5

5

Hi, I’m Ashley-Christian Hardy

In Progress…

full- stackagile.comachardy@fullstackagile.com@achardypmfacebook.com/ fullstackagile

medium.com/@achardypmpinterest.com/achardypminstagram.com/achardypm

linkedin.com/in/achardypm

Story Points1

23 5

8

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.

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.

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.

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.

3 Point Estimate

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

23

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.

The Experiment

Thank you!

Full-stackagile.comachardy@full-stackagile.com@achardypmfacebook.com/ fullstackagile

medium.com/@achardypmpinterest.com/achardypminstagram.com/achardypm

linkedin.com/in/achardypmslideshare.net/ ashlychrstn

tumblr.com/ blog/achardypmhttps://plus.google.com/ achardypm