Kanban thank you maam
Upcoming SlideShare
Loading in...5
×
 

Kanban thank you maam

on

  • 1,710 views

Talk at DevOps Melbourne May 2011

Talk at DevOps Melbourne May 2011

Statistics

Views

Total Views
1,710
Views on SlideShare
1,708
Embed Views
2

Actions

Likes
1
Downloads
10
Comments
0

2 Embeds 2

https://twitter.com 1
http://coderwall.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Kanban thank you maam Kanban thank you maam Presentation Transcript

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