Forums

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. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

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.

Velocity
Last Post 23 May 2014 06:22 AM by Pablo Rossi. 4 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Pablo Rossi
Basic Member
Basic Member
Posts:170
Pablo Rossi

--
22 May 2014 05:22 PM
    Hi, I was watching the Evidence Based Management video lately and I noticed that they said that velocity isn't mandatory within Scrum. Its not even in the scrum guide.

    My question is if we omit velocity, how does release and iteration planning gonna be done?
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1491
    Ian Mitchell

    --
    23 May 2014 12:51 AM
    Velocity is a quantifiable measure, but there's nothing in Scrum which says PBI's have to be estimated numerically. T-shirt sizes could be used for example.

    During Sprint Planning, a team have to be satisfied that they can meet the Sprint Goal. This can be a qualitative decision based on collective experience of how much work can be taken on, rather than numbers.
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1491
    Ian Mitchell

    --
    23 May 2014 12:51 AM
    Velocity is a quantifiable measure, but there's nothing in Scrum which says PBI's have to be estimated numerically. T-shirt sizes could be used for example.

    During Sprint Planning, a team have to be satisfied that they can meet the Sprint Goal. This can be a qualitative decision based on collective experience of how much work can be taken on, rather than numbers.
    Philipp Eisbacher
    New Member
    New Member
    Posts:35
    Philipp Eisbacher

    --
    23 May 2014 01:29 AM
    Hello.

    You can do iterationplanning by walking through the stories until the team does not feel comfortable anymore. I always recommend not to plan iterations based on velocity, just use it as one "verification" to get a feeling for the iteration and the progress.
    We release every sprint, so releaseplanning = iterationplanning
    But there is also no releaseplanning in scrum so there is also no need for velocity to do this "in scrum".
    Pablo Rossi
    Basic Member
    Basic Member
    Posts:170
    Pablo Rossi

    --
    23 May 2014 06:22 AM

    Posted By Philipp Eisbacher on 23 May 2014 02:29 AM
    Hello.

    You can do iterationplanning by walking through the stories until the team does not feel comfortable anymore. I always recommend not to plan iterations based on velocity, just use it as one "verification" to get a feeling for the iteration and the progress.
    We release every sprint, so releaseplanning = iterationplanning
    But there is also no releaseplanning in scrum so there is also no need for velocity to do this "in scrum".

    As the trainer said, what is not in the scrum guide doesn't mean that it is not needed. Could also mean that the focus wasn't on release management but it can still come...

    However, I'm curious when you are dealing in a "Buyer & Seller" situation where the customer comes up with a list of PBI's how do you come up with a long term forecast?
    Keep in mind that the customer can also go to your competition so if you can't give a forecast and your competitors can, then you lose the deal....

    How would this go without tracking velocity?
    You are not authorized to post a reply.


    Feedback