We stopped roadmap work for a week and fixed 189 bugs
2 hours ago
- #team productivity
- #bug fixing
- #software development
- Fixit weeks involve stopping all regular work for a week to focus on fixing small bugs and improving developer productivity.
- Rules include no bug taking over 2 days and focusing on end-user bugs/features or developer productivity.
- A points system and leaderboard gamify the process, with rewards like t-shirts for achievements.
- Recent fixit stats: 189 bugs fixed, 40 participants, median of 4 bugs per person, max of 12 by one person.
- Benefits include improved product craftsmanship, individual satisfaction from quick fixes, and boosted team morale.
- Preparation is key, with bugs tagged and sized beforehand to ensure efficiency.
- A 2-day hard limit on bug fixes prevents rabbit holes and maintains the fixit's momentum.
- Gamification elements like points and leaderboards enhance engagement without affecting performance reviews.
- AI tools help reduce context switching by quickly summarizing needed changes or even one-shot fixes.
- Criticisms addressed include the trade-off with roadmap work and the value of dedicating time to small fixes.
- Fixits are adaptable to smaller teams with shorter durations, maintaining the core benefits.