The Kanban Guide for Scrum Teams introduces 4 key movement metrics groups can use to see and enhance their movement:
Work in Progress (WIP)
The variety of work gadgets began however not completed (in keeping with the group’s definition of “Workflow”).
Observe the distinction between WIP and the WIP Restrict. The WIP Restrict is a coverage that groups can use as a “constraint” to assist them form the movement of labor. The objective of the WIP Restrict is to scale back the quantity of precise Work in Progress (WIP) — also referred to as Stream Load. The group can use the WIP metric to offer transparency into their progress in direction of decreasing their WIP and bettering their movement.
Whereas groups can straight visualize the WIP ranges over time (which I like to recommend), many use the Cumulative Stream Diagram to visualise the WIP.
Cycle/Stream Time
The quantity of elapsed time between when a piece merchandise “begins” and when a work merchandise “finishes.”
This metric is a lagging indicator of movement. It’s accessible solely after an merchandise is definitely completed from the workflow perspective (e.g., it reached a Performed lane on the Kanban board). It’s usually used to drive enchancment work and set up inside/exterior expectations concerning the group’s turnaround time on particular gadgets. The primary chart/report used to visualise and analyze Cycle Occasions is the Cycle Time Scatterplot, the place groups can perceive their Cycle Time developments and distributions and have a look at anomalies.
Throughput
The variety of work gadgets “completed” per unit of time.
Observe that throughput is the precise rely of labor gadgets with out compensation for merchandise measurement — a significant distinction between throughput and story-points-based velocity. Throughput is measured at a sure step within the workflow, usually on the end line of the workflow. Throughput will be visualized by way of a separate run chart or by trying on the angle of curves on a Cumulative Stream Diagram.
Work Merchandise Age
For presently lively gadgets — The quantity of elapsed time between when a piece merchandise “began” and the present time.
WIP and Cycle Time are basic metrics most Kanban practitioners are most likely aware of, and throughput is considerably just like Velocity.
Work Merchandise Age is the brand new man on the block. Work Merchandise Age enhances Cycle Time. If Cycle Time is a lagging indicator solely related for completed gadgets, Work Merchandise Age is a number one indicator solely related for non-finished gadgets. The fundamental concept is to offer transparency to which gadgets are flowing effectively and that are kind of “caught” even when not formally blocked.
Many mature Kanban groups gravitate in direction of taking a look at getting old data by way of quite a lot of reviews or indications on their board. Through the years, essentially the most severe Kanban device distributors have launched some methods to visualise card/merchandise age.
Age by itself is fascinating however not sufficient. We additionally need some indication of movement well being. One frequent factor to visualise is the age of the present step within the workflow, also referred to as “playing cards that did not transfer not too long ago.”
One other means to have a look at it could be to have a look at the general age however mix it with the place the work presently is within the workflow in addition to what the group expects their cycle time to be (The Kanban Information for Scrum Workforce refers to this as SLE — Service Stage Expectation). Combining all this data may help the group give attention to the gadgets which might be on the most threat of lacking the group’s expectations/SLE. For instance, to illustrate a group has an SLE of 16 days with 85% confidence. If one of many playing cards on their board is 10 days outdated, is that okay? Is it an issue? The reply is that it relies upon. If that card may be very near the tip of the workflow, it’s most likely not an issue. If it is rather near the beginning of the workflow, it’s most likely a sign of an issue that requires consideration. The “Getting old Work in Progress” chart under supplies this angle of each the place lively gadgets are within the workflow, what the standard cycle instances for this group are, and, primarily based on that, which gadgets are indications of movement dangers (clearly orange-red means very low chance of ending inside the group’s movement expectations).
To sum up, work merchandise age is one of the best metric to have a look at if you wish to decide when an merchandise that has already began goes to be completed. This contrasts an merchandise that hasn’t began — the place your greatest wager is your historic Cycle Occasions. The Service Stage Expectation is simply an expectation set by the group to themselves answering the query, “What Cycle Time can we count on to see for an merchandise of this kind, and what’s our confidence degree for this?”.
Utilizing the Stream Metrics in Typical Workforce Occasions
So, how can these movement metrics be leveraged in typical group occasions? Groups would possibly use totally different occasions, however a typical set of occasions combines some planning exercise, ongoing check-ins, a evaluation of a working product increment, and a course of retrospective/enchancment session — in different phrases, the group occasions steered by Scrum. Here is a mapping of those movement metrics that may be leveraged in these occasions:
Listed below are some extra particulars:
- Dash planning primarily leverages throughput to create a sensible forecast for the Dash backlog. Work Merchandise Age may be related when you have got some gadgets left over from the earlier Dash and need to determine what to do about them.
- The main focus of Day by day Scrum is the continued movement inside the Dash, so naturally, what we care about is what’s presently happening. Subsequently, Present WIP and Work Merchandise Age are an important metrics in Day by day Scrum.
- Dash evaluation features a evaluation with stakeholders of each the Increment and total movement habits of the group—developments in Cycle Occasions and Throughput are fascinating. Throughput will also be used as a part of launch planning/road-mapping discussions, particularly when mixed with Monte-Carlo simulations, which give some higher visibility/confidence into “What will be executed by when.” NOTE: It’s at all times necessary to emphasise that these are projections/forecasts, not commitments.
- Dash retrospective is all about inspecting and adapting the method and the workflow. Subsequently, it’s a good place to have a look at WIP, Cycle Occasions, and throughput from the angle of on the lookout for areas for enchancment.
This text launched movement metrics that any group, whether or not they’re utilizing Kanban, Scrum, home-grown course of, DevOps, or perhaps a conventional waterfall, can use to see and speed up/enhance the movement of labor. I additionally launched some concepts for methods to weave these movement metrics into the group’s routine.
