agile estimation

Farhan Sabir's picture

Mapping Story points against hour Estimation

Farhan Sabir asked on April 19, 2017 - 3:05am | Replies (1).

Hi everyone,

I have just taken over responsibility as a a scrum master and although i have worked under a scrum team before for a year but i always had difficulty in estimating according to story points. So in my first prokject as a scrum master, I took a risk and though to map story points against hours and it went very well. Here is how i mapped:

Points - Hours

1       2-4

3       4-8

5       8-16

7      16-24

9      24+

Mitch Goldstein's picture

I like your idea very much. It is similar to the way that I prefer to estimate, with two key differences:

- I recommend a 'modified' Fibonacci sequence: 1,2, 3, 4, 5 as the point scale. 8, 13 are allowed, but represent stories too big to plan. Why do I add '4'? Because 1, 2, 3, 5 has a big hole in it...

- I use the baseline recommended by the Scaled Agile Framework (SAFe) methodology of having a one-point story representing the unit of effort required to start, execute and finish a story to the definition of done in one sprint day. We loosely define a sprint day as the six hours of an eight hour day where people actually work. Thus, we allocate eight points of work during a typical sprint for a typical team member.

That said, I am amenable to making 'half-days' a reasonably consistent substitute for full days. It is important that your decisions reflect the will and planning effectiveness of the team. Always make sure to be flexible in interpreting how agile should be implemented. Also, ensure never to freak out and get brain lock over estimates. Remember - they are ESTIMATES.

@MitchSumma

[article]

Collaborative Risk Analysis for Release Planning

Summary:

Release planning is more than just stuffing the highest ranked stories into iteration buckets. To be meaningful the whole team needs to participate. Lightweight risk management techniques are not orthogonal to an agile approach They can help proactively address previously hidden concerns and the planning process benefits all-around from shared dialog on release-impacting risks.

Release planning is more than just stuffing the highest ranked stories into iteration buckets. To be meaningful the whole team needs to participate. Lightweight risk management techniques are not orthogonal to an agile approach They can help proactively address previously hidden concerns and the planning process benefits all-around from shared dialog on release-impacting risks.

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.