1. Introducing Kanban On process tuning, WIP limits and getting things done

2. Introducing Kanban a picture says more than a thousand words

3. Overview Why scrum isn’t enough Extending the process Limiting WIP Daily stand-up Deploy when ready Visualizing the flow Continuous process improvement

4. Why scrum isn’t enough Hard to commit to a two-week plan New issues on a daily basis Failing sprints due to unexpected tasks  Iterative (scrum) process seems to make no sense for a team with a high maintenance load

5. Extending the process the scrum process

6. Extending the process our kanban process

7. Limiting WIP Creating code =/= creating value Limit WIP for each state Get Things Done by aiming to reduce the WIP Reduce story size (1  5 days of development) Go with the flow, drop the time-boxing Managing WIP limits

8. Daily stand-up Scrum: (individual) What did you do yesterday What are you going to do today Are you stuck somewhere Kanban: (team) What is likely to go on and off the board today What is likely to move on the board Where is traffic stuck and how can we fix it

9. Deploy when ready Adding a WIP limit to the final step Help each other to finish the stories in the flow Not allowed to start working on new stories Self-improvement, documentation, getting coffee or food, prepare deploy, ...  Deploy when ready and tested  immediate value vs. Iterative deployment

10. Visualizing the flow Identify bottlenecks and help where needed Clear indication of project evolution to the business Recurring bottlenecks can be identified and avoided on a higher level

11. Continuous process improvement Managing WIP Managing steps in the flow Creating a consistent development pace Explicit process policies allow for critical analysis, discussion and improvement Ideas? Speak up!