Prioritize technical debt items for {{product_area}}. Debt inventory: {{debt_list}} Team capacity for debt: {{capacity}} Strategic context: {{context}} **Prioritization Framework:** **For each debt item, assess:** 1. **Impact** - Developer productivity cost - Customer-facing impact - Security/reliability risk - Velocity drag 2. **Effort** - Size of fix - Risk of fix - Dependencies 3. **Urgency** - Is it getting worse? - Blocking other work? - Compliance implications? 4. **Strategic Alignment** - Related to roadmap items? - Enables future initiatives? **Scoring Matrix:** | Debt Item | Impact | Effort | Urgency | Strategic | Priority Score | **Priority Categories:** 1. **Must Fix This Quarter** - Critical items - Justification 2. **Should Fix When Possible** - Important but not urgent - Opportunistic timing 3. **Accept for Now** - Not worth fixing yet - Monitor conditions **Allocation Strategy:** - % of sprints for debt - How to protect capacity - Measurement approach **Communication:** - How to explain debt work to stakeholders - Progress reporting
Technical Debt Prioritization
Prioritize technical debt using impact and strategic alignment
72 copies0 forks
Share this prompt:
Details
Category
AnalysisUse Cases
Debt prioritizationSprint planningEngineering health
Works Best With
gpt-4claude-3
Created Updated Shared