Story points & the evolution of agile estimation

We’ve joined leaders in the industry to unpack story points and the evolution of agile estimation.

Estimation using story points has become the most popular way for agile teams to rate the relative effort of work, instead of traditional time-based estimates.

[isaacfife]

Thanks for this video Atlassian! I really enjoyed hearing from Andrea and Mike especially.

[its_matt_long]

Great discussion - would love a visualisaton summary of this discussion (collecting my own thoughts watching this).

[jimiwikmanofficial]

I like that you bring up a failed estimation effort as a reason why you switched to Story Points. This is very often why people don't want to use Time: inability to make estimations. The thing is that replacing a time estimation with an arbitrary point system does not really change that. You will just continue doing guesstimates and never learn to do estimations.

[herihehe.]

Implementation details will surely help to avoid guesstimate pitfalls.

[timjoe]

I couldn't imagine a plumber telling me that he couldn't offer me a usd amount. Instead he would charge me 10 story points.

[jimiwikmanofficial]

Story Points is nothing more than a way to avoid accountability because you are unable to do proper and realistic estimations.

In any situation where you have resource management and need cost analysis Story point is completely useless. Any company that work with KPI's or common data Story Points are not working. So the only place this works is if you have a single product with a single team because then you don't need accountability or actual timelines.