Synchronizationand Cadence inScaled Kanban

Lean Kanban India 2015

lkin15.leankanban.com

Lean Kanban India 2015

lkin15.leankanban.com

S R V SUBRAHMANIAM

PRINCIPAL CONSULTANT - AGILE

Platform

heterogenuity

Team Size

Integration needs

Multi­department

involvement

Domain complexity

Non­functional 

requirements

Compliance

Geographical

Distribution

context ofscaling

­1­

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 Kanbanin a Program Context

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

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 Developmentby Donald G. Reinertsen

­4­

FLOWPRINCIPLES OF PRODUCT DEVELOPMENT

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 Developmentby Donald G. Reinertsen

­5­

FLOWPRINCIPLES OF PRODUCT DEVELOPMENT

Teams must moderate their throughput tomaximize program throughput

­6­

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­

Feature

Backlog

Features 

in Dev.

Features

in UAT

Features

in Integ.

Features 

Prod ready

possible program level kanban board set-upteams can have their own boards

integration happens atleast on a daily basis

­8­

Is thislane

needed?

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­

INTEGRATIONTEAM

PRIORITIZATION

PLANNING INTEGRATED DEMO RELEASE

ESTIMATION

­10­

CADENCE BASED SCHEDULING OF KEY EVENTS

VALUE DELIVERY"Decouple

from WORK ITEM VARIABILITY"

DAVID J ANDERSON

­11­

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

@srv_subbu

THANK YOU

linkedin.com/in/srvsubbu

TOUCHLET US BE IN