Boot the backlog: Optimizing your workflow for dev happiness
summary
Concrete process changes and outcomes: team at Workforce.com adopts six-week cycles with two-week cooldown, removes the backlog via a betting table and a rotating reactive team, and standardizes on Ruby on Rails plus rebuilt mobile app in Rails with Hotwire (migrated off React Native) to ship faster. Details include tech scoping, fat‑marker UI sketches, GitHub as the single comment surface, pairing for onboarding, continuous shipping during cycles, and tangible wins on speed and dev satisfaction.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:08Why processes matter
- 3:17Workflow design challenges
- 4:21Shape Up methodology
- 9:21Moving quickly as a team
- 15:22Flow State for work
- 21:21Maximizing user value
- 26:00Reflecting on improvements
- 27:24Q&A
related talks
01h 01mDitch your Backlog and Shape Up your product development
31mScaling Happy Engineering Teams
22mOptimizing Product Development: Balancing Speed, Quality, and Process
30mTransforming to a Culture of Continuous Improvement
18mAgile leadership and technical mastery, a harmonious alliance
01h 02mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
39mImplementing Programmer Anarchy
22mCreating a team mindset of continuous improvement