Kanban and flow
management skills

Kanban is a strategy for optimising the flow of value. The Kanban Guide describes three practices: defining and visualising the workflow, actively managing items in it, and improving the workflow.¹ Core techniques include a board reflecting real stages, explicit policies for each stage, WIP limits, pull rather than push, and flow metrics: work in progress, throughput, cycle time and work item age.

Little's Law explains why WIP limits work: average cycle time equals average WIP divided by average throughput, so if throughput stays the same, cutting WIP shortens cycle time.² Atlassian's guide describes how WIP limits expose bottlenecks and reduce costly context switching.³ Flow skills matter in delivery and operations roles. AmbitionBox lists delivery managers in India at a typical ₹25.1–27.7 lakh⁴ and scrum masters at ₹16.5–18.2 lakh.⁵

Kanban Guide practices

3

Flow metrics: WIP, throughput, cycle time, work item age

4

Typical delivery manager pay in India (AmbitionBox)

₹25.1–27.7 lakh

Typical scrum master pay in India (AmbitionBox)

₹16.5–18.2 lakh

Table: How Kanban skills are assessed (editorial summary)

Table: Little's Law applied to a support team (illustrative)

Table: How Kanban developed (editorial summary)

• A board that reflects a real workflow
• WIP limits you introduced
• Cycle time and throughput before and after
• An ageing work item you unblocked
• Explicit policies for stages
• A verified Kanban certificate

Show flow outcomes: "Introduced WIP limits and ageing reviews for IT support; average cycle time fell from 11 to 4 days; escalations dropped."

"Why limit WIP?"

To reduce multitasking, expose bottlenecks and shorten cycle time.

"Calculate cycle time with Little's Law."

Divide average WIP by average throughput.

"What's work item age and why watch it?"

Time in progress so far; it signals stuck work early.

"How do you handle urgent work?"

An expedite class of service with a strict limit and clear policy.

"How do you forecast delivery in Kanban?"

Use historical throughput and probabilistic forecasting rather than estimates.

• "Does the board match the real workflow?" — honesty.
• "Are there WIP limits?" — flow maturity.
• "Which flow metrics are tracked?" — data.
• "How is urgent work handled?" — policy.

Table: Flow-related roles and typical pay in India (AmbitionBox, October 2026; indicative)

Table: Common Kanban tools (editorial guidance)

• Team member / coordinator — works on a Kanban board.
• Team lead / scrum master — manages flow.
• Delivery manager — flow across teams.
• Agile coach — flow practices organisation-wide.
• Head of delivery — predictable delivery.

1. Week 1: Visualise — Map your team's real workflow and current WIP.
2. Week 2: Limit and prove — Set WIP limits, track cycle time; take the Kanban Certification.

Related: Agile and Scrum, Lean Process Improvement and Project Management. Guides: agile and Scrum, lean and project management.

• Stand-ups — walk the board right to left.
• Ageing checks — oldest items first.
• Replenishment — pulling new work deliberately.
• Metrics — cycle time and throughput trends.
• Bottlenecks — finding and fixing.
• Policies — keeping rules explicit.

"Why walk the board right to left?"

To focus on finishing work closest to done before starting more.

"What does a cumulative flow diagram show?"

How much work is in each stage over time; widening bands reveal bottlenecks.

Table: A first-90-days plan (editorial guidance)

Start with an honest board and baseline metrics. Introduce WIP limits gradually and discuss ageing work daily. Then find the biggest bottleneck and address it, and begin forecasting from throughput data.

AI tools can now spot ageing work, predict which items are likely to miss deadlines and suggest where bottlenecks are forming, using board history. They can also triage incoming tickets, routing them to the right queue and reducing waiting time at the start of the workflow.

These tools work only if the board reflects reality and policies are clear. Teams still decide WIP limits, classes of service and improvement priorities. AI-assisted work can also shift bottlenecks — for example, faster coding may expose slower review or testing. In interviews, show how you'd use AI insights to act on flow problems sooner, while keeping humans in charge of policies and priorities.

Start by measuring current WIP per stage for a couple of weeks. Set initial limits slightly below current levels — often around one to two items per person in active stages — and agree them as a team experiment. When a limit is reached, people help finish existing work rather than starting new items. Review after two to four weeks: if work regularly stalls, adjust policies or limits; if cycle time falls, consider tightening further. The aim isn't perfect numbers but a team habit of finishing before starting.

Replenishment is where a Kanban team decides what to pull into the system next. Hold it on a regular cadence, often weekly. Review capacity first: how many items are finishing and how much room the WIP limits leave. Then look at the ordered list of candidate work with the people who request it — product, support or business owners — and agree which items enter next and why. Check that each item is clear enough to start, with known acceptance criteria. Keep urgent work in an explicit expedite class with its own strict limit rather than letting it bypass the process. Short, predictable replenishment meetings stop new work from leaking in sideways and help requesters trust that their needs will be handled in order.

Over time, compare what was pulled with what was finished. If items keep returning blocked or unclear, improve the readiness check. If the queue of candidates is always enormous, discuss saying no or archiving old requests, so the team's commitments stay realistic.

"Kanban means no planning." Kanban teams plan through replenishment, service levels and forecasting from throughput data.

"WIP limits slow us down." They usually speed up delivery by reducing multitasking and waiting.

"Kanban is only for support teams." Development, marketing, HR and leadership teams all use it to manage flow.

"A board is Kanban." A board without WIP limits, explicit policies and flow metrics is just a task list.

• Boards that hide real stages.
• No WIP limits.
• Ignoring ageing work.
• Using flow metrics to blame individuals.
• Pushing work instead of pulling.

Kanban practices come from the Kanban Guide; Little's Law from queueing theory; WIP guidance from Atlassian; and India pay from AmbitionBox (read October 2026). The worked example, WIP guidance and history are editorial. Science of Apps publishes the free test linked here. Last reviewed October 2026.

• Kanban — a visual, pull-based strategy for optimising flow.
• WIP limit — a cap on work in progress.
• Cycle time — time from start to finish of an item.
• Throughput — items finished per period.
• Work item age — time an item has been in progress so far.