Shaping Up Your Development Process With Shape Up
summary
Pinnacle21 adopts Shape Up with six-week builds plus two-week cooldowns, enforcing a strict appetite (time) limit and 25% elective cooldown time so technical debt gets paid down. Work arrives as a written pitch and a bi-monthly betting table chooses projects; carryover is forbidden. Examples: a UI triptych fix shifts a flow that had 90% of users hitting the wrong button, a rollout of 20 five-question in-app quizzes (with confetti) ships and improves onboarding, and releases are batched every six months for regulated customers.
AI-written summary · about
chapters (11)
- 0:00The failure of agile
- 2:42Common agile traps
- 7:36Introduction to shape up
- 12:30Managing time and scope
- 17:50Cycles and cooldowns
- 20:15Adopting shape up at scale
- 24:09Organizational structure
- 29:27Release and project flow
- 32:18The betting process
- 39:25Monitoring and feedback
- 47:51Real-world examples
related talks
01h 01mDitch your Backlog and Shape Up your product development
31mApplying Shape Up in the Real World
32mStop Running in Circles: Applying Shape Up
45mShaping the Work: Assigning Whole Projects, not Tasks - keynote
39mShape Up: How to Ship Fast Without Burning Out
16mDitch the Backlog – Stop Sprinting and Start Shaping (⚡️)
21mScaled Agile DevOps
26mHelp! We have a QA problem