Your SlideShare is downloading. ×
0
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Myfirstkanban
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Myfirstkanban

609

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
609
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • What happens when people try out Kanban? (for the first time?)
  • Bank
    Back office
    Accounting rules engine
    Bureaucracy
    Waterfall or anarchy? We started doing XP / Scrum
  • By end of iteration – a lot of stories had piled up in “Ready for Review”
  • W (average time in the queue) = L (average number of things in the queue) / λ (average processing rate)

    http://scalingsoftwareagility.wordpress.com/2009/12/14/an-agile-illusion-how-that-nice-backlog-is-actually-decreasing-your-team%E2%80%99s-agility/
  • Benefits and drawbacks
    WIP limits needs to have buffer
    However, nice when stories have been completed / reviewed over night. Works best with India handing stories over to UK..
    Hard to explain Kanban to other locations.
    Cultural and political differences. Some people like C&C. Personal Agendas.
    Repeating message over and over again helps.
  • By measuring only from Ready For Dev -> Done (but done was only Done with Development) we encouraged the wrong behavior
    People were splitting stories too much
    People did not think all the way to production – features were essentially not working
  • Span the whole process
    Break down silos and project boundaries
    Encourage communication
  • Transcript

    • 1. My First Kanban Erling Wegger Linde
    • 2. @erlingwl
    • 3. Inspiration: finance.groups.yahoo.com/grou p/kanbandev/
    • 4. Context
    • 5. Process .. -> In dev -> Ready For Review -> Done -> ..
    • 6. Motivation .. -> In dev -> Ready For Review -> Done -> ..
    • 7. Introducing Kanban 10 .. -> In dev -> Ready For Review -> Done -> ..{ Limit WIP Visualize Pull Flow
    • 8. How we sold it Wq = Lq/λ +
    • 9. Evolving 10 10 .. -> Ready For Dev -> In dev -> Ready For Review -> Done -> .. { {
    • 10. Problems with tools
    • 11. Distributed Team
    • 12. Local optimizations
    • 13. Always look at the whole
    • 14. How I hoped it would evolve 5? 10? 8? 5? Idea -> Analysis -> Development -> Testing -> In production
    • 15. Questions? • http://erlingwl.wordpress.com/ • @erlingwl • http://uk.linkedin.com/in/erlingwl

    ×