Menu
Tomek's blog
  • Contact & About
Tomek's blog
Photo by Charles Deluvio on Unsplash

Simple & Powerful Sprint Capacity Planning Technique

Posted on February 2, 2021February 8, 2021 by Tomek Kaczanowski

Disclaimer: I will not go into the story points (SPs) pros/cons battle. If you use SPs (or T-shirt sizes) you might find this technique useful. If you don’t then this post is probably of no value to you.

I know some teams that plan their sprint based on the number of story points (SPs) that they finished in the previous sprint(s). So if they finished 30, 27, 32, and 31 SPs in the previous sprints they will consider everything close to 30 a reasonable number but they would reject the idea of taking 40 SPs. And rightly so.

I believe this is not enough, at least not enough if your stories vary in size. I mean, if all your stories are estimated to 1 point, then I guess such a sprint capacity planning is all you need. But if not – and in the majority of cases that I’m aware of it is not – then you need something more.

1+1 != 2

Why? Because story points don’t sum up so easily. Closing a story estimated to 5 is not the same as closing five stories each estimated to 1. First of all, because in general SP is a pretty rough estimate. Second, because it might take a different way of working to be proficient at dealing with 5s than at dealing with 1s. Writing five short stories is not equal to writing a novel.

Size Matters

So, what could we do about it? Ah, there is a simple technique that could help you. So basically, you should remember not only the number of story points delivered in the previous sprints, but also the distribution of stories, like this:

So now you know much more. As we can see there is a mixture of stories of different sizes which the team is able to deliver during a sprint. For example, we can see that during one sprint the team never finished a story of 13 SPs and never delivered more than two stories of 8 SPs. Which makes you cautious to agree with committing to a sprint of 2 stories of 13SP and 1 of 5 SP, even if it sums up to a “reasonable” number of 31 SPs.

TIP: Of course, you could (and probably should) add some more info to this simple spreadsheet, i.e. keep track of ppl availability so that you know how absence affects team’s ability to deliver.

That is it, have a nice day!

P.S. Size of stories

Long story short, there are two most widely used measures of story sizes.

First, there are the numbers from Fibonacci sequence:

http:///mathisfun.com

Second, you could use T-Shirt sizes, using 3 (S, M, L) or more sizes, e.g.:

https://nirbhaygandhi.com/

Share this:

  • Twitter
  • Facebook
  • LinkedIn
  • Reddit
  • Pocket
  • Email
  • Print

Like this:

Like Loading...

Related Posts

  • agile
  • estimation
  • planning
  • scrum
  • scrum sprint
  • team
  • tips & tricks
  • Leave a ReplyCancel reply

    Follow me on Twitter

    My Tweets

    Subscribe to Blog

    My Books

    Practical Unit Testing - JUnit Practical Unit Testing - TestNG Bad Tests, Good Tests kanban for your team 1,2,3 kanban Złe testy, dobre testy

    Tags

    4dx agile book review capacity planning conference constraints continuous improvement daily scrum decision taking discussion effectiveness review estimation experiment facilitation feedback funny getting things done goals interview kanban leadership management management 3.0 meetings notes organisational culture procrastination productivity psychological safety rant remote work retrospective scrum scrum sprint sociocracy sociocracy 3.0 team testing tips & tricks tools transparency visualization wip work in process work in progress

    There is no Planet B. Act Now!

    There is no Planet B. Act Now!
    There is no Planet B. Act Now!

    Follow me on LinkedIn

    Tomasz Kaczanowski

    Top Posts & Pages

    • Journey Lines - A Team Building Activity
      Journey Lines - A Team Building Activity
    • 4DX: LAG vs. LEAD
      4DX: LAG vs. LEAD
    • The Progress Principle: Making Progress in Meaningful Work
      The Progress Principle: Making Progress in Meaningful Work

    Categories

    • agile (32)
    • book (7)
    • event (2)
    • facilitation (2)
    • organization (11)
    • productivity (32)
    • sociocracy (10)
    • team (5)
    • testing (2)
    • tools (16)
    • Uncategorized (9)
    • varia (30)
      • remote work (2)
      • ux (2)

    No Business On A Dead Planet

    No Business On Dead Planet
    No Business On Dead Planet
    ©2025 Tomek's blog | WordPress Theme by Superb Themes
    %d