• Like
  • Save
A Kanban Primer
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

A Kanban Primer

  • 157 views
Published

A workshop Jeff Patton and I facilitated at Qcon 2009 in San Francisco. http://qconsf.com/sf2010/sf2009/presentations/show_presentationee01.html

A workshop Jeff Patton and I facilitated at Qcon 2009 in San Francisco. http://qconsf.com/sf2010/sf2009/presentations/show_presentationee01.html

Published in Software
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
157
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
0

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

Transcript

  • 1. A Kanban Primer
  • 2. Introductions Aaron Sanders Rally Software aaron@sanders.name Jeff Patton AgileProductDesign.com jpatton@acm.org
  • 3. It's About You
  • 4. What is Kanban?
  • 5. Not a New Concept
  • 6. The Kanban concept is common in Japanese culture
  • 7. Kanban Practice
  • 8. Make It Visible
  • 9. Let It Flow
  • 10. The Basic Board
  • 11. Building a Kanban Board
  • 12. Using a Kanban board
  • 13. Display and manage cycle times • Reduce WIP Limits • Reduce size of development items • Identify and act on bottlenecks immediatel Disneyland’s public display of current cycle- times by ride
  • 14. Use cumulative flow diagrams to visualize work in progress www.agilemanagement.net/Articles/Papers/BorConManagingwithCumulat.html 14
  • 15. Use cumulative flow diagrams to visualize work in progress • www.agilemanagement.net/Articles/Pa pers/BorConManagingwithCumulat.html 15 www.agilemanagement.net/Articles/Papers/BorConManagingwithCumulat.html
  • 16. Shippable Items Aren’t Work items • Minimal Viable Product the smallest product that can generate value when shipped • Minimal Marketable Feature the smallest feature that customers and users would value • User Story or development item small, testable piece of working software, building it helps us learn
  • 17. Lean Thinking
  • 18. Breakout questions picture of a huddle or something Questions to answer in small groups - discussion + share-out When is OK to break the WIP limit What are the best ways to deal with the bottleneck? What happens when you ignore a bottleneck? Should every item be the same size? Where is Kanban appropriate? How do you know when you're done?
  • 19. Thanks!
  • 20. Make it visible