| Context | A Scrum Team is working on many tasks at the same time and productivity is low. |
| Problem | Multitasking drastically reduces productivity. Multitasking requires many context switches, so productivity gets reduced by bringing one task to a state where it can be put away for some time and (re)starting the next task requires some ramp up effort. Furthermore having a head full of many tasks which need to be done does not free the mind to focus on a few tasks to be done right. |
| Forces | too little/too much multitasking too little/too much flexibility |
| Solution | Spice up Scrum with Kanban Kanban brings two important aspects to Scrum. Transparency is increased with a Kanban board which shows tasks in a column view, representing a value chain. E.g. put Product Backlog Items in the leftmost column, Technical Tasks in the next one, followed by an “in progress” and a “done” column. By moving the cards through the columns, the teams always knows where it stands. The second aspect is the work-in-progress limit (WIP). It limits the number of cards per column. The limit can either be imposed per team member or for whole team per column. Thus multitasking is limited and productivity is increased. If the process gets stuck, the team members blocked by the WIP limit(s) switch over to supporting those members which are working on stuck tasks in order to remove road blocks. Note: The “pull pattern” from Kanban is already part of Scrum. |
| Resulting Context | The throughput of the Scrum Team increases and the Kanban board provides a higher level of transparency. |
Dieser Artikel wurde von Andreas Heilwagen am 13.11.2011 um 12:30 gepostet und unter Best-of, Praxis, Scrum eingeordnet. Sie können Kommentaren über den RSS 2.0-Feed folgen. Das Posting steht unter der Creative Commons-Lizenz wenn nicht anders vermerkt.
