Back to Forum

Velocity

Last post 05:05 am September 8, 2014 by Alper Gurbuz
3 replies
danouche
12:33 pm June 9, 2014

i should stop reading on the subject, the more i read the less i know. some contradictory info is now making me doubt in my basic logic capacities :P

is anything false here?

1- velocity is used by dev team to estimate how much work they can add in a Sprint backlog
2- the only purpose of velocity is to help p.o. make forecast (!!!)
3- velocity is updated by anyone that sees it needs to be updated
4- velocity of a spi can only be accounted for when the spi is done (which is the same as 'when the po considers it done'

(i find #2 to be a little extreme, by saying that its the "only" purpose.. but i can see how it can be useful to the po)

thanks!

Ludwig Harsch
10:24 am June 10, 2014

2 is false, because of 1.
3 is phrased misleading. Of course it has to be "anyone" from the Scrum Team.
What is a spi?

Ian Mitchell
11:27 am June 11, 2014

I think Danouche means PSI, or Potentially Shippable Increment

Alper Gurbuz
05:05 am September 8, 2014

2 seems false.
Not sure whether 3 is true though. PO is responsible for tracking the product performance as clearly stated in scrum guide.
I can imagine potential conflict between the dev team and PO when ticking a PBI as done.
Since velocity should only account the done PBIs, it falls into PO's area.
I think to avoid any conflicts most sensible approach would be the PO to update the velocity during or just after the review meetings.

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.