Everyone Can Agree With This Approach To Prioritization
summary
Argues that prioritization is solved by capacity allocation not resource schedules, using Kanban boards, visible cards, and explicit WIP limits to count work items and enforce proportions (example: 20 total slots with limits like 4 of type A). Introduces classes of service (standard, due‑date, expedite, intangible), cost‑of‑delay profiles, and horizon 1/2/3 splits to allocate slots. Policy decisions on pull rules and limits settle cross‑silo conflicts, surface tradeoffs, and let maintenance, customer fixes and roadmap work coexist predictably.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 5:17Who has a stake
- 10:15Customer service
- 12:50Quarterly releases
- 15:20Resources
- 20:40Work Flow
- 24:25Work In Progress
- 26:30Capacity
- 29:05Visualization
- 36:30Value
- 43:15Discovery
- 51:05Cost Delay
related talks
30m10 Different Techniques for Choosing What to Start Next
18mEffective backlog prioritisation for company happiness
43mSoftware Engineering Management at Scale with the Theory of Constraints
45mPortofolio Kanban, The Art of Being Loosely Coupled and Highly Aligned
28mIntegrate and Conquer: The Power of a Unified Backlog
51mMastering Trade-offs for Scaled Agile Success
35mKanban, our way
33mPrioritizing Effectively and Forming a Product Vision