Velocity

5 posts, 0 answers
  1. John
    John avatar
    19 posts
    Member since:
    Dec 2011

    Posted 24 Feb 2012 Link to this post

    I would like to see the current Velocity displayed somewhere without having to run a report.  I believe this should be displayed in xView and would be nice to show what the Velocity needs to be in order to finish on time.
  2. Ryan
    Admin
    Ryan avatar
    164 posts

    Posted 24 Feb 2012 Link to this post

    Hello,

    When you say velocity do you mean the total estimate of all stories completed in an iteration? Because if so, then to complete on time your velocity must be equal to the total stories estimate, a value that is displayed on the xView.

    Perhaps you would like to see what percentage of these stories are done vs not done? Or are you looking for a comparison between this iteration and the previous iterations' velocity, similar to what the Velocity Report shows?

    Kind regards,
    Ryan
    the Telerik team
    New Cross Project Perspective in TeamPulse coming soon!
    Want to know how TeamPulse could help you better track all your projects?
    Reserve a seat for the TeamPulse R1 webinar today!
  3. John
    John avatar
    19 posts
    Member since:
    Dec 2011

    Posted 27 Feb 2012 Link to this post

    What I am looking for is an additional method for my developers working on an iteration that is off schedule to know how much work needs to be accomplished in order to meet the due date.  Take for example a 10 day 50 point iteration.  On day 1 in order to meet the due day at least 5 points need to be finished each day to meet the due date.  But lets say no work gets accomplished for 2 days, now in order to meet the due date 6.25 points need to be accomplished.  When a iteration starts to slip I would like I way for the development team to know how much more effort (velocity) is needed to get the iteration back on schedule in order to meet the due date.
  4. Steve
    Admin
    Steve avatar
    24 posts

    Posted 27 Feb 2012 Link to this post

    Hi John,

    Thanks for the reply. We now better understand your needs.

    Unfortunately, we deliberately decided to take a different approach with xView. Instead of calculating an optimal number that your developers can attempt to meet, we show you what you're not going to get based on your actual historical trends. We additionally allow you to set what date you start receiving alerts on so that you can only start to worry once you have enough historical data to be accurate. For a 10-day iteration, looking at what was produced on the first 2 days really shouldn't cause you to start worrying about your velocity.

    With xView, you can communicate to your stakeholders what they can expect to receive when the deadline comes and work with them to make the right choices. Do you stop working on a low value feature or do you cut scope in a high value feature that scheduled to be delivered past the original due date. You can work with them to decide what’s important to them and communicate the challenges early so that there aren’t any nasty surprises.

    It's been our experience that once an iteration really starts to slip, telling your developers that they need to "work harder" seldom gives you the desired result. What’s more likely to happen is that the developers will “agree” to work harder, but they’ll either overestimate their ability to increase what they produce (and still be late) or they’ll cut quality to get things “done”. Either way, your stakeholders are in for a nasty surprise.

    All the best,

    Steve
    the TeamPulse Product Owner
    New Cross Project Perspective in TeamPulse coming soon!
    Want to know how TeamPulse could help you better track all your projects?
    Reserve a seat for the TeamPulse R1 webinar today!
  5. John
    John avatar
    19 posts
    Member since:
    Dec 2011

    Posted 27 Feb 2012 Link to this post

    My development team prides itself on almost always meeting deadlines without loss of quality or removing items.  The current tool provides the feature I was speaking about and our developers use it religiously to keep on task.  I would like to think that the addition of an optional setting like this in a future release of xView would be a worthwhile addition for those teams that are similar to my team.
Back to Top