Story Points … again

Strugling with “complexity” vs. “effort” or how to really apply story point estimation?

Heres a nice article about it:
https://www.scrumalliance.org/community/articles/2017/january/story-point-estimations-in-sprints?feed=articles

Excerpt:

If Story Points = fun(Effort) and Effort = fun(Size, Complexity), then Story Points = fun(Size, Complexity)

Effort

5
An extremely large story
Too large to be estimated accurately
A definite contender to be broken down into a set of smaller stories
May be a candidate for separation into a new project

1
A very small story representing tiny effort level
It may take a few hours of work

Complexity

5
Extremely complex task
Multiple dependencies on other stories or systems
Requires a skill set that is missing in the team but important
Story is difficult to accurately describe
Many unknowns
May require high level of refactoring
Extensive research required
Requires difficult judgment calls
Story implementation might have significant impact outside its scope

1
Very straightforward
Crystal-clear technical and business requirements
No unknowns
No research required; jump directly at task
Basic programming skills required
Effects of the story are confined to the story itself

This blog is a digital memory for me. I store nuggets of information, ideas and resources on these pages so that I can access and share them easily at any time, from everywhere. I always felt a strong passion for continuous improvement and that is why I am now super happy to be a professional Scrum Master. Scrum, Kanban, Agile Project Management, Coaching, Learning and Self Management are my passions and that is also what my blog is about ...

Leave a Reply