CTO/CIO. Ruby. Rails.
just some more awesome
An agile project that is converting points into real units of time is potentially dysfunctional because it’s a sign that a) the advantages of the points/velocity system aren’t being fully utilized or b) the business team is having too much influence on the creation of estimates, or possibly worse. It’s possible that things are still okay, but the presumption is that this estimation style does not encourage good agile practice.
Noel's post hits on a lot of good points. Somewhere in me, I have a response (or addendum) to it . . . when I have time ;)
The biggest problem with Agile is that it is misunderstood by the business. The business wants Gantt charts, which implies accurate predictions of the future. As long as the business stays Waterfall, points will always eventually be converted to real units of time. Why? It is the only way to answer the question, "When will this be done?"
CTO/CIO. Ruby. Rails.
CTO/CIO. Ruby. Rails.
Theme created for Posterous by Obox
