Skip to main content

SP estimation varies between teams

Last post 02:21 pm January 19, 2023 by Martin Jungmair
5 replies
12:53 pm January 18, 2023

Hi, In our organization different teams estimate story points differently. Management requested us to align the method of estimation so it won't be that one team develops 20 SP and the other 40 SP in the same sprint. What do you think of this? can we align the method?

04:57 pm January 18, 2023

Story Points aren't developed, usable increments of value are. Why do management care about the numbers that are used?

As long as their estimation technique helps Developers get their arms around how much work they can take on, what more do management need to know?

06:06 pm January 18, 2023

Story Points are a means for Developers to estimate their work.  Once work begins, those estimates are no longer useful because new information is obtained that could potentially impact their initial estimate.  Story Points should not be used for anything beyond the Developers deciding if they think they can get that work done in a Sprint. 

As @Ian points out, no one should focus on how many Story Points are in a Sprint.  What matters is how much value is being created and delivered during the Sprint.  As Scrum Masters, you should educate "Management" about how the Developers are self-organizing and self-managing their work in order to deliver value that the stakeholders want. 

Going to leave this here for you to read as inspiration for the discussions with your fellow Scrum Masters and Management.

01:02 am January 19, 2023

Why does management want the teams to align on their method of estimation? What do they hope to accomplish or achieve? Chances are, there are better ways to do what they want than to align on the definition of a story point.

07:47 am January 19, 2023

Thank you all for putting the time to answer, will share this with my colleagues :-)

02:21 pm January 19, 2023

I would not recommand aligned SP estimations. I know such requirements from management and my experience is that an relative estimation with computable values always leads to missunderstandings even if you try to explain it.

Maybe SP does not fit for your company. SP can help, but the Scrum Guide does not mention them.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by may have their access revoked at any time, without warning. may, but is not obliged to, monitor submissions.