January 20, 2023

In a webinar in the present day, somebody stated that Velocity is evil if equated with productiveness.  I disagree.  And partly agree.


First some explanations (quick, possibly too quick for some):

The Velocity of a dash is the variety of story factors that the workforce “earned” (accomplished) that dash.

Well, I’d say Velocity is absolutely the common velocity during the last 3 sprints. It is the real-world productiveness of the workforce given all the actual world points (eg, regardless of loads of impediments).

It’s a part of the sport, and offers transparency.

Nothing in life is a exactly correct metric. All “enterprise” metrics are much less exact than a number of scientific metrics, usually.

Still, a tough measure might help information motion.

Poor Estimation

It is true that some groups are poor or weak at estimating.   For this quick publish let simply say that that may be fastened (rather a lot) in a comparatively quick time.

There are quite a lot of different key components in utilizing Story Points nicely.


Compared to itself (in prior sprints), an upward productiveness motion ought to be mirrored in an elevated Velocity (for the Team).

If the Team makes use of SPs pretty nicely.

By productiveness, we imply “work models” (SPs) accomplished per dash (eg, in 2 weeks or 10 enterprise days).

Is could be very correct?  No.

Accurate sufficient to be helpful?  I believe sure.

Other Productivity Measures

The extra necessary productiveness, actually, is BV delivered.  Business worth delivered to the client in a while field (eg, per 3 months).

But folks by no means name this “Velocity”.

Can Velocity be used badly?

It will be and it’s used badly. Regularly.

We talked about the poor estimating.  At some level this poor estimating appears intentional.

Managers wish to use velocity to match groups.  No, don’t do this.

Managers can “demand” that velocity enhance by X%.  Demanding that is incorrect and silly.  Asking about and supporting (in helpful methods) the continual enchancment that results in notably greater velocity is cheap.  But simply saying “work more durable” is often each imply and silly.  (If a supervisor says “I believe your workforce ought to work more durable on X” — that may very well be the beginning of a helpful dialog.)

Other Problems

If a supervisor places strain on Velocity, Teams generally lower high quality to realize the purpose.  Bad!

But this and different comparable issues will be averted with somewhat consideration.

Good Uses

The Team can set a purpose for itself to extend velocity by fixing impediments.

The Team can benefit from the recreation of the dash, and really feel “small wins” because the rating (accomplished SPs) goes up.

If the Team “wins” the Sprint (ie, completes the SPs they dedicated to), they need to rejoice.  And that helps.

The Team can see if they’re flatlining.  Not good within the hospital, not good for a Team.

If a Team has improved rather a lot, they could begin to compete with a few of the finest Teams of their space (metropolis, state, nation).

To be truthful, it’s exhausting to match groups in an apples-to-apples manner.  But the aggressive vitality (if affordable) and the will to enhance by observing what “they” do, might help us get rather a lot higher.


Life is a recreation. Never take it too severely.  You win some, you lose some.

But most individuals wish to play video games. Games with scores. And we (eg, we in enterprise) can use that to assist construct an awesome workforce.  Or a significantly better workforce.



It is unimaginable to persuade some folks not to hate story factors.

But I hope these quick phrases assist some.





« « What is Scrum? – by Ken Schwaber || What if one Team member doesn’t agree with the method? (eg, to do “scrum”) » »

Source link