KANBAN DEVELOPMENT or get the agilest from agile Oleh Dovhai, Java developer, ex QA engineer - about Kanban development process and how to use it in your project . We will learn: · What Kanban is: origin, principles, practice · Kanban vs Scrum: compare tools for understanding, not judgment · There is no ideal tool: experiment, combined and again experiment

1. KANBAN DEVELOPMENT
get the agilest
from agile

2. History
● Kanban is descended from The
Toyota production system
● kan - visible, visual; ban - card or
board
Primary goals:
❏ reduce the amount of work in progress (WIP)
❏ visualization of production
❏ optimize the process

3. A simple example

4. Goals
● Optional (big tasks,
aspiration, etc).
● E.g. provide support IE,
Integration with social
networks

5. Story queue
● Tasks ready to development
● The highest task has the
highest priority

6. Acceptance scenarios
● Test cases

7. Development
● Development
● Autotests

8. Test
● Testing
● Covering

9. Done
● The task passed all phases.
● All work on the task are
completed.

10. One day in Kanban-land

11. Ok, lets work...

12. The process is started

15. A few minutes latter...

16. some problems...

18. The process is stopped

21. A few days latter...

22. Kanban vs Scrum: main differences
● Kanban has no sprints
● Kanban has no team speed
● In Kanban time estimation is optional
● Scrum has no WIP limit

23. Scrum board

24. Kanban board

25. Kanban we are using

26. Cards we are using

27. Radiator

28. Our speed (points/week)

29. Literature
● Mary Poppendieck - Leading Lean software development
● Kent Beck - Extreme Programming Explained
● Henrik Kniberg - Kanban vs Scrum

30. Thank you
● Skype: o.dovgaj
● dovgaj@gmail.com
● facebook.com/o.dovgai
● vk.com/id4876979