Skip to main content

scrum problem sprint

Last post 10:26 pm September 28, 2018 by Simon Mayer
7 replies
11:55 pm July 19, 2016

You are the Scrum Master and your Development Team of 6 members has completed six Sprints with the
following information:

Sprint 1: 10 pontos
Sprint 2: 11 pontos
Sprint 3: 15 pontos
Sprint 4: 14 pontos
Sprint 5: 15 pontos
Sprint 6: 10 pontos
The remaining story points for product development total 42. What is the approximate number of Sprint
required to complete product development?

A. 6
B. 3
C. 5
D. 4

Why is 4 the correct answer ?


03:31 pm July 20, 2016

What do you know about team velocity, and using that reflective metric to forecast completion of future work?

I would read up on that subject, and the answer should then make sense to you.

Also, the Scrum Guide does not recognize velocity, so it is my guess that the above exam question originates from one of the many "offshoot" Scrum organizations/sites. You should be wary of any information such sites provide regarding Scrum.


08:48 pm August 1, 2016

4 Sprints *could* be a valid answer, and it's certainly possible to work back from this and deduce one or more methods which *would* give this result.

But what significance does the stated team size, or being a Scrum Master, have to the velocity calculation?


09:47 pm August 1, 2016

Hey ana,
the average is 12.5 points, so in 4 sprint the team will probably achieve around 50 points. 3 are not enough as it adds up only to 37.5

Michael


05:52 pm August 3, 2016

The average of last 3 sprints is 13. To complete 42 points you need 3.23 sprints which is nothing but 4.


12:55 pm September 28, 2018

Hi,

The average velocity is  12.5 points,

remaining Points are 42

So, 42 /12.5 = 3.36  ... make it round so 4

so in 4 sprints, the team will achieve all points ++. 3 are not enough 

Subha


10:22 pm September 28, 2018

While 4 seems like the most logical answer, what I don't like about this question is this: why would the Scrum Master be forecasting how many Sprint remain?  


10:26 pm September 28, 2018

Recent sprints have shown that it is possible that the team deliver 10 points worth of work. This has happened twice, so we should not consider it a fluke.

Therefore, it is possible that the next 4 Sprints all result in 10 points of work being delivered, which would not be enough to reach the milestone of 42 points. There is therefore a chance (albeit a small one) that based on historic data, the milestone will only be reached after (or during) the fifth Sprint.

Conversely, it has been proven that 14 or more points worth of work may be delivered in a Sprint. This has actually happened three times. So there is a reasonable chance that the milestone will be reached within three Sprints.

It can be helpful to convey the likelihood of such outcomes. So rather than just taking the average, you could say the forecast is that the milestone will be reached within 3 to 5 Sprints.

Techniques, such as the Monte Carlo method can be used to simulate the chance of each potential outcome, based on historic data.

Also, don't forget that however you model it, you can only make a prediction. No amount of calculation can give you 100% certainty.


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.