Integrate and Conquer: The Power of a Unified Backlog
summary
Claim: a single prioritized backlog cuts duplicated work and clarifies priorities across merged teams of 220 people. Practical moves: pick one tool (Jira), create multiple Jira views for leaders, PMs and teams, purge old items (one cleanup removed 47 three‑year‑old tickets), and keep roadmaps as living views. Prioritization uses known frameworks (RICE was suggested), cadence matters (monthly personal review; phased org rollout over weeks), and the cleanup demonstrably improves delivery and focus.
AI-written summary · about
chapters (11)
- 0:00Unified backlogs introduction
- 3:14Personal backlog chaos impact
- 7:13Unified backlog concept
- 9:23Fragmented team backlogs reality
- 11:53First steps to unify backlogs
- 15:23Multiple Jira views
- 17:30Cleaning outdated backlog items
- 19:39Living roadmaps over slides
- 21:26Tailoring views for different roles
- 23:35Start small embrace change
- 24:17Q&A on prioritizing backlogs
related talks
18mEffective backlog prioritisation for company happiness
50mFree your mind and the rest will follow - delete your backlog
20mHow We Transformed Strategy and Aligned the Company
33mPrioritizing Effectively and Forming a Product Vision
57mEveryone Can Agree With This Approach To Prioritization
36mOk, I’ve Burned My Roadmap and My Backlog. Now What? Lean Product Management
52mToo many cooks! Supporting augmented teams without getting salty
01h 00mAgile Project Management Anti-Patterns