Back to Forum

dropped stories during the sprint and velocity measure

Last post 06:35 pm February 23, 2018 by Ian Mitchell
1 reply
Fanis Alefragkis
02:46 pm February 23, 2018

Let's say that at the beginning of the sprint the team commited to 5 stories of 10 story points each. The ideal team velocity for that particular sprint is 50 if all stories are done. In the middle of the sprint the team agrees with PO to drop 2 of the stories and add another one from backlog of 5 story points. If the sprint is finished with all the other stories completed (30 story points) and the adhoc one of 5 points what is the teams velocity? Is it 35 or 30 based on the original commitment??

Ian Mitchell
06:35 pm February 23, 2018

If the 5-pointer they added is of value to the Product Owner, can you think of any reason not to take it into account when ascertaining the team's velocity for that product?

Why though would a team commit to stories of a certain estimated size? What sort of commitment is that, and why would it be useful? Aren't stories planned into a Sprint just a forecast of the work thought necessary to meet the Sprint Goal?

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.