This document discusses using Kanban principles and practices to improve productivity, quality, and time to market for product development projects. It presents Kanban as an alternative to "Push" organizations that lack transparency and empowerment. Key Kanban elements discussed include visualizing workflow, limiting work-in-progress, managing flow through prioritization and forecasting, responding to changing priorities through expediting and swarming, using multi-level boards, and implementing feedback loops and governance. The document provides an overview of how to start implementing Kanban through systems thinking and modeling the current workflow.
6. www. .xyz
PUSH VS PULL ORGANISATIONS
In Push Organisations
• Decision making in isolation
• Lack of visibility and transparency
• Unclear expectations and goals
• Lack of economic prioritisation of projects and misalignment with
strategic goals
• Lack of empowerment and enablement of employees to meet
expectations
7. www. .xyz
PUSH VS PULL ORGANISATIONS
In Pull Organisations
• Teams self-organise based on capacity and capability
• Equal contributors to the problem-solving process
• Maintain their commitment
• Create engaging environment with passion & excitement
• Predictability
• Probabilistic planning & forecasting
• Smooth journey from concept to cash
12. www. .xyz
VISUALISATION
Merits in visualising your Portfolio:
• Visualise the stage of each project in the portfolio
• Identify which projects are blocked
• Raise awareness of the bottlenecks
• Align projects with teams
• Highlight the current workload
• Resolve interdependencies
• Prioritise projects based on economic drivers
• Classify projects by their nature using colour aids
14. www. .xyz
LIMIT YOUR WIP
Set WIP Limits:
• Balance the demand for more work with the capacity to deliver
quality products
• WIP Limits create a coordination mechanism
• Enable a pull-based system
• Sustainable teams working in a productive and predictable
environment
• WIP Limits signal availability & expose issues
• Focus on flow and not on utilisation
15. www. .xyz
“
“Avoid futility of endless busyness, make time to
renew, find time gaps to reflect, take advantage
of slack to respond to change.
– Stephen Covey
16. www. .xyz
MANAGE FLOW
• Manage your portfolio with valuable data
• Prioritisation made on economic value (e.g. Cost of Delay, Cost of
Carry, Real Options)
• Identify and manage different types of projects (e.g. S/M/L or
Internal/External)
• Understand your system (Cumulative Flow Diagrams, Lead Time
Distributions)
• Accurate Probabilistic Forecasting of Project Completion
17. www. .xyz
RESPONDING TO BUSINESS PRIORITIES
33∞ 4 12- 2 6-
Pre-Project Feasibility Foundation Post-ProjectDelivery Deploy
Expedite à à à à à
18. www. .xyz
MANAGE FLOW
Expedite projects:
• Expedite projects that have a business-critical impact
• Expediting provides a means to respond
• Swarming on the project
• ACT!
19. www. .xyz
33∞ 4 12- 2 6-
Pre-Project Feasibility Foundation Post-ProjectDelivery Deploy
Expedite à à à à à
PROJECTS IN PROGRESS
20. www. .xyz
MANAGE FLOW
Use Project Swimlanes to limit projects in progress (PIP):
• Visualise and manage team workloads
• Focus on completing projects
• Avoid project multi-tasking
• Coordinate multi-project deployments
21. www. .xyz
33∞ 4 12- 2 6-
Pre-Project Feasibility Foundation Post-ProjectDelivery Deploy
Expedite à à à à à
Goal Backlog In Prog
TRACKING PROJECT PROGRESS
22. www. .xyz
MULTI-LEVEL (NESTED) BOARDS
33∞ 4 12- 2 6-
Pre-Project Feasibility Foundation Post-ProjectDelivery Deploy
Expedite à à à à à
Goal Backlog In Prog
To-Do Doing Done
To-Do Doing Done
To-Do Doing Done
23. www. .xyz
MANAGE FLOW
Connecting the PMO & Delivery perspectives:
• Detailed work at team-level board
• Regularly prioritised backlog based on business value
• Interfaces well with Scrum teams:
• Tickets in the PMO board form the Sprint Goals or the Sprint
Backlog stories
• Potentially Shippable Increments (PSI) from Scrum teams
contribute towards Deploy phase
24. www. .xyz
33∞ 4 12- 2 6-
Pre-Project Feasibility Foundation Post-ProjectDelivery Deploy
Expedite à à à à à
Goal Backlog In Prog
To-Do Doing Done
To-Do Doing Done
To-Do Doing Done
EXPLICIT
POLICIES
EXPLICIT
POLICIES
EXPLICIT
POLICIES
EXPLICIT
POLICIES
EXPLICIT
POLICIES
GOVERNANCE & QUALITY
25. www. .xyz
EXPLICIT PROCESS POLICIES
Definition of Done for each stage aligned to the products
E.g. a policy for moving between Feasibility and Foundations would
be to have completed the following products:
• Outline Business Case
• Risk Assessment
• Outline Solution
• Feasibility Prototype (optional)
• Outline Plan
• Project Approach Questionnaire (PAQ)
27. www. .xyz
WHERE TO START
STATIK
Systems Thinking
Approach to
Implementing Kanban
Design Kanban System
Classes of Service
Model Workflow
Demand & Capability
Opportunityto Improve