Skip to main content

Story Point estimation when more than 1 works at the story

Last post 11:51 am March 13, 2017 by Justin Müller
3 replies
02:44 pm March 6, 2017

Hi there

How are You handling storys, which will be developed by more than 1 person?

Example:

A discovery story, 3 engineers has to make a workshop together.

Now they are estimating 3 points for it. But because they are 3 peoples, we sum it up to 9.

Is this really correct?

 

 

 


04:36 pm March 6, 2017

In Scrum it is the Development Team which does the work, hence it should be a team estimate. So if it is clear that all 3 engineers must be involved, then each ought to estimate on that basis, and not just for their own bit of the work.

Where planning poker cards are used, it might thus be reasonable to expect them to play 8s or 13s.

It seems strange though to have a "discovery story" which is "developed". Isn't this workshop something the team and Product Owner would hold in support of Product Backlog Refinement?


07:16 pm March 6, 2017

Is "discovery story" another name for "spike"?


11:51 am March 13, 2017

Yes, it's the same like a spike


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

Please note that the first and last name from your Scrum.org 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. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org 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 Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.