Kanban Flashcards
Kanban overview
1) Scrum without timebox
2) Value stream start from where are you currently at
3) Kaizen (continuous improvement)
4) No retrospection (retrospection happen at every time)
5) No time boxes for team, but cycle time is used
6) But time box for single item
7) Work processed in small chunks
8) Minimize rework and delay
9) System throughput matters
Kanban visualization
1) Capacity of the team
2) What team is working on, challenges faced with out micro managing
3) Clear priorities with Kanban
4) What is the availability
5) bottlenecks in value stream
6) Dependencies becomes clear
7) Cards can be features, task or user stories
limit WIP
1) reduce waste
2) increase focus
3) swarming vs some WIP
Kanban solution
1) on demand meetings only (only regular stand up)
2) prevents prematurely designating work as complete
3) clear quality bars at each step
simple work flow
1) Take an item from backlog
2) Specify work necessary to implement it
3) Implement it
4) Validate that it works
5) deliver
Set limits on chaos
1) by limiting work in progress (add WIP as last step in problem solving)
2) Scrum - time box
Run daily standups
1) any one can run
2) no milestones, no sprints and no retrospectives
External bottleneck
Items are moved to the Track column whenever they are blocked awaiting external input. Tracked items don’t count toward the Implement WIP limit
parking lot
Occasionally, it becomes apparent that an item will be blocked indefinitely. We have a special area for those items in the corner of the signboard. We call it the “parking lot.” Every few weeks, we check on the status of parking lot items, but we don’t do this daily
Deadlines and WIP
Limiting WIP also constrains your team’s size (your costs) and reduces your cycle time (the time for a planned work item to go from specification through validation). Shortening cycle time benefits quality, agility, and customer engagement. It also allows you to accurately measure throughput, and thus accurately estimate completion dates.
Minimum viable product
your MVP is the set of work items (note cards) in your backlog that must be completed before release. That is, regardless of the monetary or market impact, you would delay or cancel your product release if those work items were incomplete.
Priority
Ordering these cards in your backlog is a team activity. Leadership, internal and external partners, and customers help you prioritize the cards into the big buckets, but day-to-day execution belongs to the team.
Calculate your task completion rate
count the number of tasks that are done with their final step within any two-week to four-week period, and divide by the number of days.
How soon will a work item be addressed and done
(active tasks + estimated task for the work item and work items ahead of it) / task completion rate
when will a significant product release be completed
(active tasks + estimated task for the MVP workitems) / task completion rate
