1. Kanban methodology in sustaining projects Volodymyr Lysak 06/2014

2. Agenda  What is Kanban?  Kanban board  Difference between Kanban and SCRUM  Positive and negative sides of Kanban  Agile methodologies in sustaining projects

3. What is Kanban?

4. is a scheduling system for lean and just-in-time (JIT) production (Wikipedia definition)leanjust-in-time a just-in- time method of inventory control, originally developed in Japanese automobile factories (Random House Dictionary)just-in- time control in manufacturing, a written set of specifications and requ irements for production of a commodity and inventory control of the components needed; a manufacturing system or assembly line using such written specifications; also called just-in-timejust-in-time in manufacturing, a written set of specifications and requ irements for production of a commodity and inventory control of the components needed; a manufacturing system or assembly line using such written specifications; also called just-in-timejust-in-time

5. What is Kanban? Kan - visually Ban - board

6. How long is it used in the world? 1959 from 1959 year

7. How to ensure quality? Where is control?

8. Japanese mentality

9. How it works?

10. Kanban board

11. To Do (QA Review) Let’s start from tasks

12. To Do (QA Review) In ProgressDone (Ready to Merge) And add statuses

13. To DoAnalyze (Planed) In Progress Comple ted VerifyDone Add processes

14. To DoAnalyze (Planed) 2 In Progress 3 Comple ted 4 3 4 Verify 2 Done And WIP limits WIP limits

15. Difference between Kanban and SCRUM

16. Main differences  Value of rules/principles  Meetings  Estimation  Time for sprint  Process control

17. Main differences  Value of rules/principles  Meetings  Estimation  Time for sprint  Process control

18. Positive and negative sides of Kanban

19. Strong and week sides We don’t spend time for a meeting Only 3 rulesIt’s a self-regulated system Diagrams isn’t necessary It isn’t for lazy people Any type of control kills main benefits

20. Agile methodologies in sustaining projects

21. What do we usually use? SCRUM XP RUP Kanban?

22. Why Kanban? Change your mind Scrum doesn’t work Fail with sprint delivery Priorities can’t be frozen No general picture of progress Working overtime Long project

23. Who can Kanban? They already follow the rules

24. What Decision? SCRUM-BAN

25. Scrum-ban

26. More information ▪ Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results by David Anderson, 2003 ▪ Priming Kanban by Jesper Boeg, 2011 ▪ Aspects of Kanban by Karl Scotland, 2011 ▪ Scrumban: Essays on Kanban Systems for Lean Software Development by Corey Ladas, 2008 ▪ http://www.slideshare.net/GiulioRoggero/how-a-kanban- board-works http://www.slideshare.net/GiulioRoggero/how-a-kanban- board-works ▪ https://www.youtube.com/watch?v=rxE25JbSDxs&list=UUZnOY qct9R9b4IluQX7b1fQ&index=4&feature=plcp https://www.youtube.com/watch?v=rxE25JbSDxs&list=UUZnOY qct9R9b4IluQX7b1fQ&index=4&feature=plcp

27. Questions?