Applying scaling techniques for product management
summary
Project is budgeted for 15 months with a 5-person core team (2 BAs, 2 devs, 1 part‑time PM/PO) and initial scope of 10 reports; process uses Jira and Excel. Kanban is scaled by adding visual blocker tickets and explicit unblock policies, expanding the board left/right and creating an ideation group to decide priority. A two‑phase commitment and a five‑ingredient planning recipe (lead time, start, desired delivery, window, cost of delay) cuts lead times from 220/40 days variance and lets the team deliver 15 reports within the same budget.
AI-written summary · about
chapters (14)
- 0:00Kanban case study intro
- 3:20Why Kanban suited constraints
- 5:09Three scaling dimensions
- 7:17Breaking blocker paralysis
- 9:05Commitment and feedback loops
- 10:08First release lead time chaos
- 11:33Four work categories
- 13:42Process redesign with business
- 16:35Prioritizing work recipe
- 19:48Balancing customer vs capacity
- 21:33Small pieces reduce failure demand
- 22:36Kanban across teams
- 23:59Kanban flexible tool
- 25:06Q&A on lead time and policies
related talks
47mThe Only 2 Things needed to Scale Agile
22mOrganizational Inspect and Adapt for a Rapidly Growing Product — Six Months of Scrum@Scale in SmartHR's Labor Domain: Realities and Prospects
11mSpecification nightmare
46mScrum & Lean Startup in Action: Design to Delivery in 6 Months
45mFrom plan-based to discovery-based Agile portfolio management
34mThinking more product: Moving from Scrum to dual-track Agile
26mFrom Backlog to Product
39mProduct Teams: Complete Guide to Fantastic “Creatures”