Tag Archives: administration

Kanban learnings – Running multiple projects hides impediments

Posted on by

Basically the orgininal Kanban board:

Kanban with overcommit

Was reduced to:

Kanban checklists

Posted on by

(Shall be visible with the glance of an eye)

  • Do we have a bottleneck? (look for congestion/queues)
  • Do we have an impediment not dealt with?
  • Are we keeping our work in progress limit (WiP)?
  • Are priorities clear?

Iteration planning (1/week or on need basis)

Expected outcome:

  • Prognosed delivery date given to PO if needed.
    (Use size/velocity or tasks * cycle time)
  • Stories is broken down and estimated


  1. Update charts (velocity and cycle time)
  2. Remove done stories/tasks off kanban board
  3. Lookback last week [max 5 min]
    (What happened? Are we satisfied? Should we adjust WiP limit?)
  4. Team picks one thing to improve on for upcoming week [max 2 min]
  5. Write this down on top of Kanbanboard
  6. PO reads new stories to team
  7. Team breaks down and estimates stories [30 min]
  8. PO revises priorities and makes them visible


  • Can all team members do the broken down tasks?
  • Is WiP limit visible on board?
  • Can we see if we exceed WiP limit at any time?

Daily standup

Expected outcome

  • Impediments are surfaced so we deal with them
  • Team members can share experience of problems earlier encountered
  • NEVER takes more than 5 min (takes some training but is doable)


  1. What did I do yesterday
  2. What will I do today
  3. Do I have an impediment?
  4. As a team, do we need to act?


  • "60sek rule", you have 60s to offer advice to other team members if you can help them
  • All other matter : face2face after daily standup

Doing 45 minute sprint planning

Posted on by

  1. Hand out the epics (we typically have 2-3 per week)
  2. Assign one senior and one junior for each epic
  3. Forming a group per epic by letting rest of team choose from interest, but allow no larger than four members in per group
  4. Let each epic team do breakdown and size estimation
  5. Swap epic between the teams and review (we typically let one person stay and explain)

45min sprint planning

This has worked out really well. The energy and intensity of the discussions was raised significally. So far we have managed to keep our 45 time window almost every time. .A bonus is that the review almost every time have results in an changed task or a reestimation.  Thereby showing the value of a second opinion with an outside angle.