Doc Norton wrote:Team Joy
Geoff McKay wrote:
(where the scope of work is not well defined, as can be the case with Agile or iterative projects)
Doc Norton wrote:Measuring individual velocity won’t tell you who is actually contributing to the team, who is improving process, or even who actually delivers the most stories, but it will encourage your team to make collaboration a secondary concern at best.
Doc Norton wrote:...most of what impedes the work is queues and system level impediments that are generally unrelated to the work. For organizations where issues exist such as extensive infrastructure lead times, limited stakeholder availability, or crossteam dependencies, there is almost no correlation of duration to the size of the work.
"Effort and duration are rarely correlated, much less equivalent."
you wrote:Velocity isn’t about measuring the team. It is about having a coarse-grained forecast.
Doc Norton wrote:Or drinking your own Champaign, eating your own cake, driving your own car, ...
you wrote:Velocity is the rate at which a team delivers value to the customer. A team that completes many tasks, but delivers no value to the customer should have a zero velocity.