kanban - how to coordinate with kanban

Coordinate with Kanban

Kanban - Chapter 7

7.1 Visual control and pull

7.1 Visual control and pull

• Classes of service• Service class• Status information• Team member

7.1 Visual control and pull

• target self-organization

• enable team members to autonomously pull work

7.2 Eletronic tracking• extended

possibilities• limit reached, ticket

overdue, …• collect data to

create metrics and reports for management

7.3 Daily Standup Meetings

• usually mornings• typical questions up to now:

• What did you accomplish yesterday?• What do you plan on doing today?• Are you blocked? Do you need help?

7.3 Daily Standup Meetings

• those three questions are obsolete• changes since last meeting are visible if

you attend regularly• new focus on the workflow

7.3 Daily Standup Meetings

• moderator (PM) goes from right to left through the board

• focus on blockers and tickets that are behind schedule

• stuck tasks => new blocker?• mature teams only look at blockers and bug

tickets => large number of participants possible

7.4 Follow-up Meeting

• spontaneous • small group of 2-3 persons• generates ideas for improvement and

leads to process adjustments and innovation

• discuss blockers, technical problems, questions regarding architecture

7.5 Supply Meeting

• prioritization: fill input queue• PM, Dev, Department or Product Owner• quite regularly (trust, reduces coordination

costs) => later on when needed

7.6 Release Planning Meeting

• delivery at the end of value chain• use checklists or frameworks to simplify

planning (what’s ready for release; risks; emergency planning; …)

7.7 Triage• useful for bugs, but primarily for backlog

maintenance

• what to keep, what to remove

• small backlog => prioritization easier

• automation possible

7.9 Sticky buddies

• Home office => how to update physical board?

• sticky buddy gets contacted via IM, … and asked to update board

7.10 Synchronization across many time zones• key is electronic system• update physical board at least once a day• standup meetings via (video) telco; update

board beforehand

Conclusion• best practice: physical and electronic/online

board

• Kanban possible with distributed team

• regular meetings => reduce coordination costs, increase participation

• independent prioritization and release planning

Conclusion• daily standup meetings: discuss problems,

blockers, ticket flow• stand-ups: with whole team => possibility to

suggest improvements• backlog maintenance with periodic triage =>

easier prioritization• boost core competence: handle, escalate, solve

problems