Effective TODO selection: A Kanban story
summary
Team abandons per-API swimlanes, combines Android and Linux work, and uses a tactile paperboard Kanban with a four-item todo (three product items plus one internal improvement) filled daily after standup. Backlog splits into a real backlog and an under-consideration column whose items must be groomed, sized (t-shirt sizing) and championed. Result: far fewer low-value debates, faster selection from the top dozen clear items, and measurable cross-functional throughput improvement.
AI-written summary · about
chapters (8)
- 0:00Wprowadzenie
- 0:18Some Necessary Background
- 1:08Exception - Divide by Function Error
- 1:52Exception - Divide by Type Error
- 2:25Getting Validation on Board
- 3:14Keeping Everyone (Too) Happy
- 5:32The Long List That Would Not Fill Up
- 8:58A Clean Backlog is a Happy Team's Backlog
related talks
35mKanban, our way
30mTaming the Chaos: Beyond the Quick Wins
38mExpect the Unexpected! A Method for Handling Unplanned Work
48mAre You Really Using Kanban, or Just Making a List of Issues?
43mApplying Agile out of development
33mTaming The Chaos: After The Quick Wins
49mBaking Boards: Tweak the Recipe for Agile Development
47mMinimum Viable Process