Bug and Improvement Prioritization Guidelines
These guidelines are designed to ensure steady progress and product quality while maintaining development speed for new features.
Work Allocation
We allocate part of each 3-week cycle to bugs and improvements across all projects. This allocation is flexible and adjusts based on issue priority:
- Urgent: Address immediately, may exceed planned allocations.
- High: Resolve by the end of the cycle; 20% allocation.
- Medium: Address as capacity allows; 10% allocation if only medium-priority issues remain.
- Low: Tackle after feature development is complete; no dedicated time.
The key is to stay agile. While we plan these allocations during sprint planning, we're always ready to adjust for urgent issues. This approach helps balance resolving user pain points and technical debt with advancing feature development.
Prioritization Process
Each project maintains its own issue queue. At the start of each cycle, we prioritize based on severity and impact:
- Urgent: Blocking issues, crashes, security risks.
- High: High-impact performance or UX enhancements.
- Medium: Non-blocking bugs with workarounds.
- Low: Minor convenience or polish improvements.