This document discusses using Kanban principles to manage knowledge work and the balance between discovery and delivery. It introduces different types of knowledge work from exploiting existing knowledge to exploring new knowledge. It then discusses using various "Discovery Kanbans" to visualize and limit work-in-progress for ideas, experiments, decisions, and actions to balance upstream discovery with downstream delivery. Different approaches are needed depending on what is known versus unknown in the work.
4. Software development is knowledge work
Ref.: Allistair Cockburn
4
Users &
Sponsors
Testers
Business
Analysts
Programmers
UI
Designers
Detailed decisions
about function
and data
Decisions
about program
structure
Detailed
decisions about
external
appearance
Decisions
about function
and style
Decisions
about system
correctness
The knowledge discovery process
10. Kanban principles and practices
10
Ideas Reday
for Dev
Development
Testing
Ready
for UAT Done
ongoing done
5 ∞
Abandoned
5
3
A user
story
A bug
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A bugA user
story
A user
story
A user
story
A user
story
• Visualize
• Limit WIP
• Manage Flow
• Make Process Policies Explicit
• Implement Feedback Loops
• Improve Collaboratively, Evolve
Experimentally (using models/
scientific method)
• Start with what you do now
• Agree to pursue incremental,
evolutionary change
• Initially, respect current roles,
responsibilities & job titles
Core practicesFoundational principles
11. Ideas Ready
for Dev
Development
Testing
Ready
for UAT Done
ongoing done
5 ∞
Abandoned
5
3
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
A user
story
Delivery kanban - focus on “work”?
11
A user
story
WORK items
Limit WORK in
progress
40. Not all Kanban is alike
Delivery Kanban
Discovery Kanban
Visualize work
Limit work in progress
Manage flow of work
Organize feedback loops
Evolve experimentally
Visualize decisions and options
Limit unvalidated assumptions and
decisions in progress
Manage flow of decisions and options
Explicit feedback loops, customer
feedback loops
Mixed change
41. Not all Kanban is alike
Delivery kanban
Discovery kanban
Improving fitness for
purpose of service delivery
Improving the fitness for
purpose of organizations in
a continuously changing
landscape
Demand is established and there is
more demand than capability
Not just delivery against established
demand but also dealing with
uncertain demand