Kanban is a popular agile way of working that focuses on visualising work, managing flow, and delivering value continuously. Within the PRINCE2 Agile Foundation context, Kanban is recognised as one of the common agile approaches teams may adopt alongside frameworks like Scrum. The term Kanban origi…Kanban is a popular agile way of working that focuses on visualising work, managing flow, and delivering value continuously. Within the PRINCE2 Agile Foundation context, Kanban is recognised as one of the common agile approaches teams may adopt alongside frameworks like Scrum. The term Kanban originates from Japanese, meaning 'signboard' or 'visual card', and it emphasises transparency and workflow management rather than fixed timeboxes. Kanban rests on core principles: visualise the workflow (typically using a Kanban board with columns representing stages such as 'To Do', 'In Progress', and 'Done'), limit work in progress (WIP), manage and measure flow, make process policies explicit, and continuously improve through feedback loops. Flow-based working, closely associated with Kanban, focuses on the smooth, steady movement of work items through the system from start to completion. Unlike iteration-based approaches that batch work into fixed sprints, flow-based working delivers items individually as they become ready, reducing bottlenecks and enabling faster response to change. Limiting WIP is central to this: by capping how many items are worked on simultaneously, teams reduce multitasking, improve focus, and expose blockers quickly. Key flow metrics include lead time (total time from request to delivery), cycle time (time actively spent working), and throughput (items completed per period). These metrics support forecasting and continuous improvement. In terms of the Agile Mindset, Kanban and flow embody principles of transparency, collaboration, incremental delivery, and responding to change. For Project Management, they provide predictability and control while remaining adaptive. In Organizational Change, Kanban is valuable because it is evolutionary rather than revolutionary; teams start with existing processes and improve gradually, which reduces resistance and eases adoption. This makes Kanban particularly suitable for organisations transitioning toward agile ways of working, supporting sustainable, incremental transformation while maintaining alignment with PRINCE2's governance and management-by-stages structure.
Kanban and Flow-Based Working
Kanban and Flow-Based Working is a core topic within the PRINCE2 Agile Foundation syllabus, appearing under the agile mindset, project management, and organizational change themes. Understanding this concept helps you appreciate how work can be managed continuously and visually, which is essential when integrating agile ways of working with the structured governance of PRINCE2.
Why It Is Important Kanban is one of the most widely used agile methods, and PRINCE2 Agile expects candidates to understand it alongside other approaches such as Scrum. Kanban supports the agile mindset by emphasizing transparency, continuous delivery, and incremental improvement. In a project context, it helps teams visualise their work, spot bottlenecks, and deliver value smoothly rather than in fixed time-boxed batches. For organizational change, flow-based working reduces waste, improves predictability, and encourages a culture of continuous improvement.
What It Is Kanban is a method for managing and improving work across human systems. The word Kanban is Japanese for "signboard" or "visual card". It originated in Lean manufacturing (notably the Toyota Production System) and has been adapted for knowledge work and software development.
Flow-based working means work items move continuously through a workflow from start to finish, rather than being grouped into fixed iterations. The goal is a smooth, steady flow of value to the customer.
Kanban is built on a set of core principles and practices: Core Principles: - Start with what you do now. - Agree to pursue incremental, evolutionary change. - Respect current roles, responsibilities, and job titles. - Encourage acts of leadership at all levels.
Core Practices: - Visualise the workflow (typically using a Kanban board). - Limit work in progress (WIP). - Manage flow. - Make process policies explicit. - Implement feedback loops. - Improve collaboratively, evolve experimentally.
How It Works A Kanban board is the central visual tool. It is divided into columns representing stages of the workflow, such as "To Do", "In Progress", and "Done". Work items are shown as cards that move across the board from left to right as they progress.
Work In Progress (WIP) limits are set on columns to restrict how many items can be worked on at once. This prevents overloading the team, reduces multitasking, and highlights bottlenecks. When a WIP limit is reached, no new work can be pulled in until existing work is completed — this is called a pull system.
Key metrics used in Kanban include: - Lead time: the total time from when a work item is requested to when it is delivered. - Cycle time: the time taken to actually work on an item from start to finish. - Throughput: the number of items completed in a given period. - A Cumulative Flow Diagram (CFD) is often used to visualise flow, WIP, and bottlenecks over time.
Unlike Scrum, Kanban has no prescribed roles, time-boxed sprints, or fixed ceremonies. It is a continuous, evolutionary approach that can be layered onto existing processes. This makes it particularly useful in environments with unpredictable or continuous streams of work, such as support and maintenance.
Kanban in PRINCE2 Agile PRINCE2 Agile recognises Kanban as a valid agile delivery approach that can be used within the stages and work packages of a PRINCE2 project. The visual, flow-based nature of Kanban complements PRINCE2's emphasis on controlled progress and management by exception. Teams may use Kanban to manage the delivery of products while PRINCE2 provides the surrounding governance and direction.
Exam Tips: Answering Questions on Kanban and Flow-Based Working - Know the six core practices and be able to identify them in scenario questions, especially "visualise the workflow" and "limit WIP". - Understand the pull system concept: work is pulled when capacity is available, not pushed onto the team. - Distinguish Kanban from Scrum: Kanban has no time-boxes, no prescribed roles, and focuses on continuous flow, whereas Scrum uses fixed sprints and defined roles. - Learn the key metrics: be clear on the difference between lead time and cycle time, and know that throughput measures completed work. - Watch for scenario keywords such as "bottleneck", "too much work at once", or "continuous flow" — these usually point toward WIP limits or managing flow. - Remember the purpose of WIP limits: they improve flow and expose problems, rather than simply restricting productivity. - Read the question carefully: Foundation-level questions are often knowledge-based (definitions and principles) rather than application-based, so precise terminology matters. - Eliminate wrong answers: if an option describes fixed iterations or specific agile roles, it is likely describing Scrum, not Kanban.
By understanding both the theory and the practical mechanics of Kanban and flow-based working, you will be well prepared to answer exam questions confidently and to apply these concepts within a PRINCE2 Agile project environment.
