Using Trac for Kanban
Upcoming SlideShare
Loading in...5
×
 

Using Trac for Kanban

on

  • 3,936 views

This is for a lightning talk for the DC Python Meet-Up.

This is for a lightning talk for the DC Python Meet-Up.

Statistics

Views

Total Views
3,936
Views on SlideShare
3,854
Embed Views
82

Actions

Likes
3
Downloads
30
Comments
0

9 Embeds 82

http://simple-is-better.com 59
url_unknown 5
http://www.slideshare.net 4
http://twitter.com 4
http://xianguo.com 3
http://paper.li 3
http://www.simple-is-better.com 2
http://a0.twimg.com 1
http://www.docshut.com 1
More...

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

Using Trac for Kanban Using Trac for Kanban Presentation Transcript

  • Kanban + Trac = Nice Fit
    Paul Boos – EPA/OPP
    Boos.paul@epa.gov
    @paul_boos
  • kanban (little k); system of signaling for pulling items to be worked. Developed by Toyota. Simple pull system.
    David Anderson credited for defining Kanban (big K). Incorporates:
    • Maintains Pull
    • Focus on Quality; Definition of Done!
    • Theory of Constraints
    • Explicit Policies
    • Limiting Work-in-Progress
    • Classes of Service
    • Predictability via measurement
    • measurement = lead time
    • per class of service
    • becomes your service level agreement
  • So where does Trac fit?
  • Kanban Board ≠ Issue Tracking
    (or does it?)
  • Simple & easy
    Lots of plug-ins: visit track-hacks.org
    - Master Tickets – could be used to show
    ticket blockages
    - Custom fields
    - Typed ticket workflow
    - Notifications
    - Keywords
    - Metrics Plug-Ins (TracMetrix provides CFD for calculating Lead Time)
    Can be configured so that person moving a ticket to a state takes ownership.
    Ability to have pre- & post- hooks (e.g. prevent movement if blocked)
  • When moving to the next state,
    that person moving it takes
    ownership.
  • 1st Attempt at Virtualizingthe Kanban
  • Work-in-Progress states at top
    WIP Limit static text, use count of tickets as a comparison
    Queue states
    under
    WIP states
  • 2nd Attempt at Virtualizingthe Kanban
    (in work)