Back to Forum

Release

Last post 08:42 pm August 29, 2018 by Simon Mayer
4 replies
Pooja Reddy Pitchela
10:17 am August 28, 2018

First sprint delivered with a velocity of 15,Second sprint 15 .. The story points left to complete the release which is of 4 sprints are too high and cannot be met based on the average velocity.What will you (Scrummaster ) suggest management and Product owner ?

Pooja Reddy Pitchela
10:22 am August 28, 2018

Has this question asked in one of the interviews .I gave my answers but wanted to hear from the community as well .

Timothy Baffa
01:49 pm August 29, 2018
  • What data did the Product Owner use to suggest that the release was achievable in 4 sprints?
  • Does the "release" represent a MVP, or is it larger in scope?
  • What can be released after 4 sprints, assuming that the Development Team keeps to their initial 15-pt velocity?
  • Can any of the future PBI's be re-estimated by the Development Team based on learnings from the first two sprints?
Ian Mitchell
03:18 pm August 29, 2018

First sprint delivered with a velocity of 15

If no release-quality increment was expected until the fourth Sprint, what was delivered during the first Sprint?

Simon Mayer
08:42 pm August 29, 2018

I would challenge the idea of completing 4 sprints of work, without validating the value delivered by releasing to customers.

If the plan is to reach a particular milestone prior to releasing, I would encourage the Product Owner to collaborate with the Development Team on ways that the scope of such a milestone can be reduced.

I would ask the Product Owner to consider whether it makes sense to continue with the initiative, if it looks unlikely that a key release date will be achieved.

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.