Kanban Method for Agile PMO Flow Management Training Course

Course overview

PMOs are often asked to improve delivery predictability while managing a mixed portfolio of projects, operational work, regulatory commitments, and unplanned demand. Yet many teams still rely on status reports that show activity rather than flow: too much work starts, priorities change without visible trade-offs, dependencies remain hidden, and delivery dates become difficult to defend. This course addresses how an Agile PMO can use the Kanban Method to make demand, capacity, blockers, service expectations, and portfolio risk visible across teams and workstreams.

Participants learn to design and operate Kanban systems for PMO and project environments rather than treating Kanban as a simple task board. The course covers STATIK for service design, visualising end-to-end workflows, defining work item types and classes of service, setting explicit policies, applying work-in-progress limits, managing dependencies, and using flow metrics such as lead time, cycle time, throughput, work item age, and cumulative flow diagrams. Participants also learn how to run replenishment, delivery planning, service delivery review, and risk review cadences that support evidence-based portfolio decisions.

Teaching combines instructor-led explanation with facilitated board design, metric interpretation, PMO case studies, and group simulations using Jira Software, Azure DevOps Boards, and Kanbanize examples. Each participant develops a practical Kanban operating model for a selected PMO service, project portfolio, or delivery team. The final deliverable is a documented Kanban system design containing a workflow, board structure, policies, WIP limits, service-level expectations, metric dashboard requirements, meeting cadences, and a 90-day implementation plan.

The course is suited to PMO professionals, project and programme leaders, delivery managers, and operational managers who need better control of work flow without imposing unnecessary process overhead. It is particularly valuable where teams use Agile, hybrid, or traditional delivery approaches but need a common way to manage demand and improve predictability.

Course objectives

By the end of this course, participants will be able to:

• Design a Kanban system for a PMO service or project portfolio using STATIK
• Map end-to-end demand-to-delivery workflows and identify waiting states, hand-offs, and bottlenecks
• Define work item types, classes of service, and explicit pull policies for mixed project work
• Set and justify work-in-progress limits using capacity, flow risk, and dependency evidence
• Interpret cumulative flow diagrams, control charts, throughput trends, and work item age
• Create service-level expectations and forecast delivery using historical flow data
• Facilitate replenishment, service delivery review, and risk review cadences for PMO governance
• Produce a 90-day Kanban implementation plan with board design, metrics, policies, and adoption actions

Benefits of attending

Target competencies

Who should attend

• PMO Managers — who need a practical operating model for controlling portfolio demand and delivery flow
• Programme Managers — who coordinate interdependent initiatives and need earlier visibility of flow risks
• Project Managers — who manage competing work, changing priorities, and stakeholder delivery expectations
• Agile PMO Leads — who must connect Agile team delivery data to portfolio-level governance decisions
• Delivery Managers — who need to improve predictability across teams without relying on fixed iteration cycles
• Operations Managers — who oversee service, change, and project work competing for the same specialist capacity

Requirements and prerequisites

Participants should understand basic project delivery concepts, including scope, milestones, risks, dependencies, priorities, and resource or capacity constraints. Familiarity with an existing work-management tool such as Jira Software, Azure DevOps Boards, Trello, or Microsoft Planner is helpful, but participants do not need to be expert users. No prior Kanban certification, Agile qualification, statistical training, or software configuration experience is required. This is accessible to complete Kanban beginners; they should expect to work with realistic workflow data, simple flow calculations, and board-design exercises rather than advanced automation or enterprise tool administration.

Training methodology

The five-day programme uses short instructor-led modules followed by applied PMO workshops. Participants analyse a realistic portfolio containing planned projects, urgent regulatory work, dependencies, and constrained specialist capacity; then translate that scenario into a Kanban system. Teams map workflows, build board policies, set WIP limits, interpret cumulative flow and control-chart data, and conduct simulated replenishment and service delivery reviews. Tool demonstrations use Jira Software, Azure DevOps Boards, and Kanbanize examples. The final session converts learning into an individual 90-day implementation plan for a live workplace service or portfolio.

Course outline

Day 1: Kanban foundations for Agile PMO flow

• Kanban Method principles and evolutionary change
• PMO demand management versus project status tracking
• Systems thinking and end-to-end flow
• Sources of variability in project and operational work
• Visualising work, risks, blockers, and dependencies
• Work item types for portfolios, projects, and PMO services
• STATIK service design method

Workshop: Participants use STATIK to define the purpose, customer expectations, sources of dissatisfaction, and initial work types for a selected PMO service.

Day 2: Designing Kanban systems and policies

• Demand-to-delivery workflow mapping
• Board columns, states, queues, and swimlanes
• Definition of ready and definition of done policies
• Explicit pull policies and entry criteria
• Classes of service for urgent, fixed-date, standard, and intangible work
• Work-in-progress limits and capacity constraints
• Dependency and blocker visualisation techniques

Workshop: Participants create a detailed Kanban board design with workflow states, swimlanes, WIP limits, classes of service, and explicit operating policies.

Day 3: Measuring flow and forecasting delivery

• Lead time, cycle time, throughput, and work item age
• Cumulative flow diagram interpretation
• Control charts and percentile-based service expectations
• Throughput trends and delivery capability
• Ageing work-in-progress signals
• Little's Law for PMO flow analysis
• Forecasting completion with historical throughput

Workshop: Participants analyse a PMO flow-data pack, identify bottlenecks and ageing risks, and prepare a delivery forecast for a priority work set.

Day 4: Kanban cadences for PMO governance

• Replenishment meeting design and commitment decisions
• Daily Kanban coordination for blockers and flow
• Delivery planning based on capacity and service expectations
• Service delivery review using flow metrics
• Operations review for cross-team dependencies
• Risk review and escalation policies
• Portfolio-level Kanban governance and stakeholder reporting

Workshop: Teams run a simulated PMO replenishment and service delivery review, making prioritisation, escalation, and capacity trade-off decisions from board and metric data.

Day 5: Implementing and improving the Kanban operating model

• Kanban Maturity Model assessment concepts
• Selecting a pilot service or portfolio
• Configuring Kanban boards in Jira Software and Azure DevOps Boards
• Dashboard and metric reporting requirements
• Adoption risks and stakeholder engagement
• Feedback loops and evolutionary improvement experiments
• Ninety-day implementation roadmap

Workshop: Participants complete and peer-review a 90-day Kanban implementation plan containing their board design, measures, cadences, stakeholder actions, and first improvement experiments.

Tools & standards covered

Jira Software, Azure DevOps Boards, Kanbanize, Kanban Maturity Model

A typical training day

Live online deliveries follow the same structure in the East Africa Time zone, with shorter screen blocks and longer breaks.

What the fee includes

How you can take this course

Certification

Participants who complete the full five days receive the Skillset Development Certificate of Completion, stating the course title, course code, dates and delivery format — suitable for professional-development records and employer reimbursement.

Frequently asked questions