Kanban thank you maam

1,874 views
1,715 views

Published on

Talk at DevOps Melbourne May 2011

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

No Downloads
Views
Total views
1,874
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
10
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Kanban thank you maam

  1. 1. Kanban, thank you ma’am<br />David Lutz<br />
  2. 2. What?<br />Linux team at Lonely Planet implemented “Kanban”<br />Daily standups<br />Task Wall<br />Metrics<br />Retros<br />
  3. 3. History<br />Current Task Wall version 3.0<br />Version 1.0 Too Heavy<br />Version 2.0 Too Light<br />Version 3.0 Just Right <br />
  4. 4. Why?<br />To fix problems with current processes<br />Tasks coming into team from multiple sources<br />Poor prioritization<br />Poor visibility of workload<br />Pushy people queue jumping<br />Toxic Tasks<br />Internal projects neglected<br />Poor communication with Agile Dev teams<br />
  5. 5. Tasks coming from multiple sources<br />Service Desk tickets<br />Email<br />Walk ups<br />Instant Messages<br />Tasks for Embedded Engineer in Dev Teams<br />Production issues (incidents)<br />Internal projects and proactive maintenance<br />
  6. 6. Strict* Rules<br />Do cards in order FIFO FTW<br />No cherry picking tasks<br />2 tasks in progress per Engineer<br />If someone wants to bump priority up they need to come to standup and argue their case<br />* Strict but not completely inflexible ;-)<br />
  7. 7. What is a card?<br />Process must be lightweight to work<br />Card = task that will take > 30 minutes work but < three days<br />Less than 30 minutes = “Just Do It”<br />More than 3 days = Split it into smaller tasks<br />
  8. 8. Coloured Cards<br />
  9. 9. Columns<br />Backlog<br />In Progress<br />Done<br />Blocked<br />Waiting for Change<br />
  10. 10. Blocked column <br />Whose card is it?<br />Who or what is blocking the card?<br />Invite blocker to standup.<br />
  11. 11. Toxic Tasks<br />Poorly Defined “make it go faster”<br />Poorly Thought Out “let’s install OS/2 on the servers”<br />Tedious and boring<br />How to deal with them?<br />
  12. 12. Outcomes<br />Smaller Queue Length<br />Internal tasks getting done<br />Increased Throughput<br />Decreased Latency<br />Better communication within and between teams<br />Happy Customers <br />
  13. 13. Who am I?<br />David Lutz<br />Sysadmin and DevOpstician<br />Lonely Planeteer for another few days then looking for new gig… <br />dlutzy@gmail.com<br />twitter.com/dlutzy <br />

×