Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The Kanban Story - Ups and Downs of Implementing Kanban


Published on

  • Login to see the comments

The Kanban Story - Ups and Downs of Implementing Kanban

  1. 1. The Kanban StoryUps and Downs of Implementing Kanban<br />Starring<br />Pawel Brodzinski as Narrator<br />The Team as Themselves<br />
  2. 2. Once Upon a Time In Central Europe<br /> Once upon a time in central Europe there was a small cross-functional team, which striven after building good software despite issues they faced along the way…<br />
  3. 3. In the Meantime In Alternative Reality…<br />…there was a team which dealt with maintenance projects…<br />…there was a team which was doing project fire fighting all the time trying to escape a death march…<br />…there was a team with crazy product manager changing his mind all the time…<br />…there was a team working on multiple concurrent small projects…<br />
  4. 4. Underground<br />Allegedly<br />high-quality<br />software<br />Never-finished tasks<br />Ever-changing priorities<br />Chaotic product management<br />
  5. 5. Everything You Always Wanted to Know About Kanban But Were Afraid to Ask<br />Henrik Kniberg &<br />Mattias Skarin<br /><br />
  6. 6. It Happened One Night<br />Single afternoon, 3 rules, 1 tool<br />
  7. 7. The Kanban Is Not Enough<br /> Garbage in – garbage out<br />Kanban is not a project management methodology<br />
  8. 8. Toy Story<br />
  9. 9. In the Meantime In Alternative Reality…<br />Adjust tools for people, not people for tools<br /> There is no such thing as the best engineering approach<br />
  10. 10. Groundhog Day<br />
  11. 11. Sherlock Holmes<br />The puzzle:<br />How should we do (insert pretty much anything here)?<br />The answer:<br />I don’t know, experiment!<br />
  12. 12. The Incredibles<br />Co-location!<br />No-meeting culture<br />Best engineering practices<br />
  13. 13. Monsters, Inc.<br />Version control<br />Deployment<br />Code ownership<br />Product management<br />Setting right limits<br />
  14. 14. Love Actually<br />If you happen to<br /><ul><li>hate unnecessary formalisms
  15. 15. work in a small team of disciplined engineers
  16. 16. experience priority changes all the time
  17. 17. avoid implementing methods by the book
  18. 18. start simple and improve over time</li></ul>you may actually fall in love with Kanban<br />
  19. 19. No Country For Old Men<br />If you happen to<br /><ul><li>follow detailed process of the rest of your organization
  20. 20. work with engineers who don’t care much about craftsmanship
  21. 21. work with primadonnas
  22. 22. be a part of distributed team
  23. 23. avoid experimenting</li></ul>you may find you are too ‘old’ for Kanban country<br />
  24. 24. Based on a true story<br />Pawel Brodzinski<br /><br /><br /><br /><br />