3. Separation of Concern or Prerogatives – Is Imp
• Why to do anything
Why
• What exactly needs to be done
What
• How to do it
How
But does it work like this? Isn’t there too much of Micromanagement?
4. Kanbanizing a layered Organization
1. Synchronization –
Between Layers
2. Cadence - Through
connected Kanban
Systems
5. Kanbanizing a layered Organization – Contd..
Why
•Strategy
•Vision
•Epics
What
•Product Roadmap
•Product Backlog
•Features
How • Team Backlog
• Stories
1. Synchronization –
Between Layers
6. Kanbanizing a layered Organization – Contd..
2. Cadence - Through
connected Kanban
Systems
Epics
Features
Stories
7. Using SAFe
as Toolkit for
Org
Kanbanization
- not as
Framework
(It is free
nonetheless)
Why
What
How
12. Flow Accelerators
Visualize and Limit
WIP
Address Bottlenecks
Minimize Handoffs
and Dependencies
Get Faster Feedback
Work in Smaller
Batches
Reduce Queue
Lengths
Optimize Time in the
“Zone”
Remediate Legacy
Policies and Practices
16. In the End → Check few things
• What level are you yourself operating at in the Org?
• What metrics you are having at that and other levels of Org?
• Are you using those metrics to make decisions?
• Is there a segregation of prerogatives for all layers in your Organization?
• Are all layers working in Cadence and Synchronization?
• Are the Leaders in your Organization bringing in the alignment by talking about the Strategy and Vision?
• Can the layers in Org be Synchronized with connected requirements?
• Can the layers be connected to visualize the work?
• Does everyone in your Organization knows on WHY they are working on something?