Fokus Pokus - Shape your product Up!
summary
Team switches to Shape Up, deletes a 250‑item backlog, and runs 6‑week focus + 2‑week cooldown cycles with a small eight‑person core; decisions go through a three‑person betting table and pitches are sized to fit fixed time variable scope. Results: Angular→React migration remains 80% unfinished, a focus period change stops about 1% of panic redemptions, and overall throughput doubles delivery pace. Emphasis is on slicing work, protecting the team from meetings, prioritizing business‑owned metrics, and treating cooldowns as mandatory rest and cleanup.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:34Team context and background
- 3:23Products vs projects
- 6:16The case for a new approach
- 12:35Defining team principles
- 14:17Implementing Shape Up
- 18:16How Shape Up works
- 20:39Rituals and lessons learned
- 42:27Recap and results
- 43:25Q&A session
related talks
44mKeynote - Focus (or Stop Starting, Start Finishing)
52mFocus in a Fragmented World: A Developer’s Guide to Staying Productive
34mMinimizing Decision Fatigue to Improve Team Productivity
38mCalm at Scale
33mBuilding Sustainable Teams to Handle Uncertainty
25mHelping Product Managers to Let Go
18mManaging Change: Implementing The UXDX Model
36mHey Focus! How to get the most out of your day