kanban development
DESCRIPTION
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 experimentTRANSCRIPT
KANBAN DEVELOPMENT
get the agilest from agile
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
A simple example
Goals
● Optional (big tasks, aspiration, etc).
● E.g. provide support IE, Integration with social networks
Story queue
● Tasks ready to development● The highest task has the
highest priority
Acceptance scenarios
● Test cases
Development● Development● Autotests
Test
● Testing● Covering
Done
● The task passed all phases.● All work on the task are
completed.
One day in Kanban-land
Ok, lets work...
The process is started
A few minutes latter...
some problems...
The process is stopped
A few days latter...
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
Scrum board
Kanban board
Kanban we are using
Cards we are using
Radiator
Our speed (points/week)
Literature
● Mary Poppendieck - Leading Lean software development● Kent Beck - Extreme Programming Explained● Henrik Kniberg - Kanban vs Scrum
Thank you● Skype: o.dovgaj● [email protected]● facebook.com/o.dovgai● vk.com/id4876979