Synchronisation and Cadence in Scaling Kanban. Presented at Lean Kanban India conference in Bangalore - December, 2015. http://lkin15.leankanban.com

1. Synchronization
and Cadence in
Scaled Kanban
Lean Kanban India 2015
lkin15.leankanban.com

2. Lean Kanban India 2015
lkin15.leankanban.com
S R V SUBRAHMANIAM
PRINCIPAL CONSULTANT - AGILE

3. Platform
heterogenuity
Team Size
Integration needs
Multi­department
involvement
Domain complexity
Non­functional
requirements
Compliance
Geographical
Distribution
context of
scaling
­1­

4. Typically a Product
development or Enterprise
application development set­up
Multiple teams working on the
same code base
Key to success is in integrated
software
Dependancy management and
alignment determine the
success.
­2­
Case of
Scaling Kanban
in a Program Context

5. Rhythm of the team
events occurring in
regular cadence
Focus on integrated
work product through
synchronization
­3­
Image source: http://www.lean­manufacturing­japan.com/scm­terminology/dbr­drum­buffer­rope­theory.html
DRUM BUFFER ROPE

6. To enable
synchronization
provide
sufficient
capacity margin
Use
synchronized
events to
facilitate cross­
functional
trade­offs
SYNCHRONIZATION
Ref: The Principles of Product Development Flow: Second Generation Lean Product Development
by Donald G. Reinertsen
­4­
FLOW
PRINCIPLES OF PRODUCT DEVELOPMENT

7. Use regular
Cadence to limit
accumulation of
Variance
Schedule frequent
meetings using
predictable cadence
Use Cadence to
enable small
batch sizes
Use Cadence
to make waiting
times predictable
Provide sufficient
capacity margin
to enable
Cadence
CADENCE
Ref: The Principles of Product Development Flow: Second Generation Lean Product Development
by Donald G. Reinertsen
­5­
FLOW
PRINCIPLES OF PRODUCT DEVELOPMENT

8. Teams must moderate their throughput to
maximize program throughput
­6­

9. possible teams in a scaled set-up
Functional Teams
1....n
System QA Team
Integration Team
System QA team and Integration team support other teams in
producing Integrated software
­7­

10. Feature
Backlog
Features
in Dev.
Features
in UAT
Features
in Integ.
Features
Prod ready
possible program level kanban board set-up
teams can have their own boards
integration happens atleast on a daily basis
­8­
Is this
lane
needed?

11. Supports and signs
off on the
Integrated product
Dynamic nature of work­
to support integration
related troubleshooting
Skills on Config. Mgmt,
CI, Infrastructure set­up
& system testing /
Automation
Binding and
blending work
accross teams
­9­
INTEGRATION
TEAM

12. PRIORITIZATION
PLANNING INTEGRATED DEMO RELEASE
ESTIMATION
­10­
CADENCE
BASED SCHEDULING OF KEY EVENTS

13. VALUE DELIVERY
"Decouple
from WORK ITEM VARIABILITY"
DAVID J ANDERSON
­11­

14. Limit number of
features in
progress
Focus on
integration to
facilitate flow
Make Integration
policies explicit
Feedback loop
from fellow teams
as well
Improve
continously at
program level
Visualize at
Program level
­12­
KANBANPRINCIPLES AT PLAY

15. @srv_subbu
THANK YOU
linkedin.com/in/srvsubbu
TOUCH
LET US BE IN