KanbanAn incomplete intro

Core practices

1. Visualise2. Limit work in progress3. Manage flow4. Make policies explicit5. Implement feedback loops6. Improve collaboratively, evolve

experimentallyhttp://en.wikipedia.org/wiki/Kanban_(development)

Visualise & manage the flow

● Every work item is tracked on the board● Each state/phase has its own column● Work items are in column dep. on the state● Transitions are well-defined

Stop starting, start finishing!

Limit work-in-progress (WIP)● items per column, items per person

Benefits:● Stories are finished sooner● Value is delivered sooner● Feedback can be received faster

Kanban vs. Scrum stand-ups (1)

Scrum: “What did I accomplish yesterday?”

Kanban: the question is not necessary.

Rationale:The cards on the board tell the story. The WIP (Work in Progress) is visual.

Kanban vs. Scrum stand-ups (2)

Scrum: “What can I commit to doing today”

Kanban: the question is irrelevant.

Rationale:Work will take whatever time it will take to get done. Committing to accomplishing the work will not necessarily make it faster.

Kanban vs. Scrum stand-ups (3)

Scrum: “What are the impediments in the way?”

Kanban:That’s the only important question to ask!

Source: http://neelnarayan.blogspot.cz/2012/02/daily-kanban-stand-up.html

The stand-up recipe

● Go from the right-most column to the left● Look out for stories that were not moved since

the last stand-up● Ensure all PRs are assigned● Ask “What is needed to get this item finished”?

Recommended readingKanban: Successful Evolutionary Change for Your Technology Businessby David J. Andersonhttp://www.amazon.com/Kanban-David-J-Anderson-ebook/dp/B0057H2M70

The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win

by Gene Kim, Kevin Behr , George Spaffordhttp://www.amazon.com/The-Phoenix-Project-Helping-Business-ebook/dp/B00AZRBLHO