Buy Amaryl Without Prescription » We Always Have The Cheapest Offers In Our Online-Drugstore http://www.agileadvice.com/2009/01/23/scrumxplean/report-average-velocity-and-fail-50-of-the-time/ All Things Agile: Scrum, OpenAgile, XP & Lean Sat, 04 Feb 2012 20:29:00 +0000 hourly 1 Buy Amaryl Without Prescription » We Always Have The Cheapest Offers In Our Online-Drugstore http://www.agileadvice.com/2009/01/23/scrumxplean/report-average-velocity-and-fail-50-of-the-time/comment-page-1/#comment-2114 AgileMan Tue, 27 Jan 2009 21:11:03 +0000 http://www.agileadvice.com/2009/01/23/scrumxplean/report-average-velocity-and-fail-50-of-the-time/#comment-2114 Excellent post, Christian, and one that brought back so many memories for me! I had an especially strong reaction to: "In this case, estimation is actually estimation, not commitment or contract. The team is expected to be ahead sometimes, and behind sometimes. The upside of this is that a lot of extra time isn’t spent playing with fictional numbers. Teams are spending their efforts on delivery as quickly-yet-sustain-ably as they can, and the organization treats them as trusted professionals in this. The temptation to assume you can predict the future is seen as folly, and the estimates are used to guide overall direction, not to make outward customer commitments." because you've hit the nail squarely on its head right there. Failure to understand those few sentences, as we've both experienced in our travels, can actually make the difference between succeeding and failing at your attempt to "go Agile." Posts like this are invaluable.... in fact, you should write a book! ;-) Excellent post, Christian, and one that brought back so many memories for me! I had an especially strong reaction to:

“In this case, estimation is actually estimation, not commitment or contract. The team is expected to be ahead sometimes, and behind sometimes. The upside of this is that a lot of extra time isn’t spent playing with fictional numbers. Teams are spending their efforts on delivery as quickly-yet-sustain-ably as they can, and the organization treats them as trusted professionals in this. The temptation to assume you can predict the future is seen as folly, and the estimates are used to guide overall direction, not to make outward customer commitments.”

because you’ve hit the nail squarely on its head right there. Failure to understand those few sentences, as we’ve both experienced in our travels, can actually make the difference between succeeding and failing at your attempt to “go Agile.”

Posts like this are invaluable…. in fact, you should write a book! ;-)

]]> Buy Amaryl Without Prescription » We Always Have The Cheapest Offers In Our Online-Drugstore http://www.agileadvice.com/2009/01/23/scrumxplean/report-average-velocity-and-fail-50-of-the-time/comment-page-1/#comment-2103 Christian Gruber Sat, 24 Jan 2009 16:55:00 +0000 http://www.agileadvice.com/2009/01/23/scrumxplean/report-average-velocity-and-fail-50-of-the-time/#comment-2103 Fair enough, Jack. And personally, teams I'm working on in trusting environments usually don't need to consider such things very much (which is why I left option 3: indemnify teams' learning). But a lot of my clients are implementing Agile within a very non agile company, and "we're getting some stuff done each iteration" is no comfort, as they haven't bought into the benefits. They see fast-moving, (seemingly) uncontrolled teams who had a history of not delivering, so they're nervous. In these environments (which are all too common in my own consulting experience) you need to carefully craft metrics to purpose, in order to engineer cultural changes. So please don't worry about it if you can afford not to! And kudo's to your organization if they can have this attitude. :) Fair enough, Jack. And personally, teams I’m working on in trusting environments usually don’t need to consider such things very much (which is why I left option 3: indemnify teams’ learning). But a lot of my clients are implementing Agile within a very non agile company, and “we’re getting some stuff done each iteration” is no comfort, as they haven’t bought into the benefits. They see fast-moving, (seemingly) uncontrolled teams who had a history of not delivering, so they’re nervous. In these environments (which are all too common in my own consulting experience) you need to carefully craft metrics to purpose, in order to engineer cultural changes.

So please don’t worry about it if you can afford not to! And kudo’s to your organization if they can have this attitude. :)

]]> Buy Amaryl Without Prescription » We Always Have The Cheapest Offers In Our Online-Drugstore http://www.agileadvice.com/2009/01/23/scrumxplean/report-average-velocity-and-fail-50-of-the-time/comment-page-1/#comment-2098 jmilunsky Fri, 23 Jan 2009 20:02:00 +0000 http://www.agileadvice.com/2009/01/23/scrumxplean/report-average-velocity-and-fail-50-of-the-time/#comment-2098 This is a great blog entry and certainly makes you think about the intricacies of velocity and how you use it. I however tend to rather focus on the practical aspects of velocity and what it's there for. In my opinion, velocity (whether you're using average velocity, last sprints velocity (whatever), it's really to be used as a guideline for determining how much work you can get done in an iteration (and therefore extended to the release). It's generally accepted in Scrum circles that some sprints you're going to get more done and some less. Bottom line is, the fact that you're iterating means you're getting some stuff done more frequently and most likely more on point than doing it any other way and this builds trust in the organization. I prefer not to get caught up in the theoretical aspects on this topic. Scrum more so than most is a practical approach to software development. So i prefer to be practical in how we use things like velocity My 2 cents Jack www.agilebuddy.com This is a great blog entry and certainly makes you think about the intricacies of velocity and how you use it.

I however tend to rather focus on the practical aspects of velocity and what it’s there for.

In my opinion, velocity (whether you’re using average velocity, last sprints velocity (whatever), it’s really to be used as a guideline for determining how much work you can get done in an iteration (and therefore extended to the release).

It’s generally accepted in Scrum circles that some sprints you’re going to get more done and some less. Bottom line is, the fact that you’re iterating means you’re getting some stuff done more frequently and most likely more on point than doing it any other way and this builds trust in the organization.

I prefer not to get caught up in the theoretical aspects on this topic.

Scrum more so than most is a practical approach to software development. So i prefer to be practical in how we use things like velocity

My 2 cents
Jack
http://www.agilebuddy.com

]]>