How did splitting stories above 5 helped us

During the planning meeting, two sprints ago, after the team made their estimates, I proposed: what if we split the stories with estimates bigger than 5? Their first reaction, as expected, was: are you crazy? These are the smallest stories we can think! Ok, I said, so let’s analyse one by one…

An important statement is that the “5” here is about our team’s scale. Other teams can have different scales.

Analysis results

After the analysis, some stories that were 13 became two stories, and the sum of their estimates were in general less than 13. Also, some stories that were 8 became two stories, with their estimates’s sum also less than 8. Just in some very very special cases we kept an 8. But we struggled to split all stories above 8.

Sprint results

All stories were DONE by the end of the sprint. The main advantages of splitting big stories is that the team often cuts out most of the uncertainties by doing it, and the result often is more stories with less points, which can be translated to more velocity.


2 Responses to “How did splitting stories above 5 helped us”

  1. Ricardo Mestre Says:


    Such a coincidence! I’ve started to do exactly this with one of my teams 3 weeks ago – and with the same great results you got here.
    Great blog, and thanks for sharing.


    • tiagomjorge Says:

      Hi, Ricardo!

      It’s nice to know that another team had the same result! Thanks for the feedback! Also, it’s very nice to see that my blog is contributing to the agile community!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: