🤖 Prompt 2 of 7
Backlog Prioritization: Value-vs-Complexity Ranking
Use this when your backlog has more than 20 items and you're not sure which 5-8 actually matter for this sprint. Your Product Owner is drowning in requests. Your team needs to know what to say no to.
From the article 7 AI Prompts for Sprint Planning: Backlog to Execution
2
Prompt 2
Copy, fill in the placeholders, paste into ChatGPT or Claude.
Prompt
For each of these backlog items, rate on a scale of 1-10:
- Business value (1 = nice-to-have, 10 = blocks revenue)
- Complexity (1 = one-line fix, 10 = architectural change)
- Dependencies (1 = none, 10 = blocked by external team)
[Paste backlog items]
Now, which items should we prioritize first? Which ones should we defer
until we have more clarity? What's the one item that's high value but
we keep deferring because it 'feels' hard? Replace before pasting:
[Paste backlog items] More prompts from this article
- #1 Sprint Goal Definition: Capacity-Aligned Goal Extraction
- #3 User Story Estimation: Assumption-Surfacing Questions
- #4 Task Breakdown: Dependency and Blocker Identification
- #5 Daily Standup: Progress-and-Blockers Prompts
- #6 Sprint Review Preparation: Stakeholder-Ready Demo Prompts
- #7 Retrospective Prompts: Structured Improvement Discovery