Pillar 3 of 5
ROI Sprint Planning™
Prioritize impact, not pressure.
It's the VDS methodology for converting QVRs into planned execution. It replaces the classic chaotic backlog with a process where each sprint generates evidence of value, not just 'work done'.
Why it matters
When priorities follow pressure, the backlog fills with work that is easy to justify socially and hard to justify by outcome. A visible score does not make the decision for you, but it makes the reasoning something the team can discuss and challenge.
- •Maximum return on development investment
- •Elimination of backlog waste
- •Objective prioritization based on data, not opinions
- •Greater predictability in deliveries
- •Total alignment between business objectives and technical execution
- •Significant reduction of low-impact deliveries
How it works in five steps
- 1
List the candidates
Collect the QVRs or initiatives competing for the next sprint or cycle.
- 2
Score the impact (1 to 10)
How much would this move the metric that matters? Use the Canvas KPI as the reference.
- 3
Score the effort (1 to 10)
How much work, risk and coordination does it take? Include dependencies.
- 4
Calculate Impact / Effort
Divide impact by effort and rank the list. Ties and surprises are good conversation starters.
- 5
Adjust and decide
Consider risk, urgency and learning value, then commit to the top of the list and record why.
Worked example: three candidates
- •One-click reorder button: impact 7, effort 3, score 2.3.
- •Loyalty points redesign: impact 8, effort 8, score 1.0.
- •New homepage banner: impact 3, effort 2, score 1.5.
- •Reading: the reorder button goes first. The loyalty redesign needs to be sliced into a smaller QVR before it competes.
Illustrative example, not real data.
Try the score
Move the sliders to see how Impact / Effort changes. Both are scored from 1 to 10.
Score5 / 5 = 1.0
What is ROI Sprint Planning™?
It's the VDS™ methodology for converting QVRs into planned execution. It replaces the classic chaotic backlog with a process where each sprint generates evidence of value, not just "work done".
Why is it fundamental?
Because the problem isn't development speed, but delivering what doesn't generate value.
A team can be ultra-productive and still not move metrics. ROI Sprint Planning™ solves:
- Sprints without clear objective
- Deliveries that aren't used
- Backlog without criteria
- Requirements without value
- Demotivated teams
Principles of ROI Sprint Planning™
1. One sprint = one deployed QVR
No partial deliveries. Each sprint delivers something that impacts a real metric.
2. Impact first, effort later
We don't prioritize by "difficulty". We prioritize by:
VDS Priority Formula:
Score = (Estimated Impact / Estimated Effort) × Strategic ROI
Where:
- Estimated Impact: How much it will move the metric (0-10)
- Estimated Effort: Story points or days (0-10)
- Strategic ROI: How critical it is for business (0-10)
Result:
- Score > 5 = High Priority
- Score 2-5 = Medium Priority
- Score < 2 = Review hypothesis
3. Mandatory post-deployment measurement
Each QVR includes:
- Target metric
- Current baseline
- Expected goal
- Measurement date
- Tracking dashboard
4. Impact-based retrospective
Not just "what we did well", but:
- Did the metric move?
- How much?
- What did we learn?
- What to do now?
ROI Sprint Planning™ Process
Before the Sprint
- Canvas Review: PO presents QVRs prioritized by impact
- Priority Score: Score is calculated for each QVR
- Feasibility Validation: Team evaluates effort and risks
- QVR Selection: Choose the highest score that fits in the sprint
During the Sprint
- Daily standup focused on progress toward the QVR
- No distractions from other requirements
- If impediment arises, escalate quickly
- Mandatory continuous integration
After the Sprint
- Impact Review: Not "it works", but "it moved the metric"
- Retrospective: What can we improve for the next QVR
- Next Planning: The cycle repeats
Differences from Traditional Scrum
Traditional Scrum
- ❌ Vague sprint goal — "Complete 10 stories"
- ❌ Priority by effort — "Let's do the easiest first"
- ❌ Velocity measurement — Story points per sprint
- ❌ Technical review — "This works, let's move to production"
- ❌ Generic retrospective — "What went well, what didn't"
ROI Sprint Planning™
- ✅ Measurable goal — "Increase checkout conversion by 15%"
- ✅ Priority by impact/effort — Systematically calculated score
- ✅ Value measurement — Movement of real metrics
- ✅ Impact review — "Did the metric move? How much?"
- ✅ Value retrospective — "How to generate more impact faster"
Proven benefits
Better business-technology alignment
- Everyone understands the "why" of each sprint
- Stakeholders see results every 2 weeks
- Fewer alignment meetings
Reduction of irrelevant deliveries
- Priority score filters low-impact work
- Smaller and more focused backlog
- Less "refactors for the sake of refactoring"
Greater team motivation
- See their work generate real impact
- Clear objectives
- Recognition based on value, not effort
Practical case - E-commerce company
Context: An online clothing store wants to increase sales this quarter.
Development options:
- Completely redesign the homepage
- Add abandoned cart reminder via email
- Create internal statistics panel for marketing
The team performs ROI Sprint Planning™:
Options analysis
Redesign homepage:
- Estimated Impact: 7 (could improve somewhat)
- Effort: 8 (several weeks)
- Strategic ROI: 0.87
- Score: (7/8) × 0.87 = 0.76 ❌ Low priority
Abandoned cart:
- Estimated Impact: 9 (direct recovery)
- Effort: 3 (simple integration)
- Strategic ROI: 3.0
- Score: (9/3) × 3.0 = 9.0 ✅ High priority
Internal panel:
- Estimated Impact: 6 (insights for team)
- Effort: 5 (internal dashboards)
- Strategic ROI: 1.2
- Score: (6/5) × 1.2 = 1.44 ⚠️ Review
Result: Abandoned cart is prioritized because:
- Has greater impact on sales
- Requires little effort
- It's a high-conversion classic
In the next sprint:
- Cart recovery is implemented
- Launched in 2 weeks
- After 4 weeks, more sales are visible
Later, the redesign can be invested in. First, quick win with high ROI.
Use it this week
Work it with the Assistant
Apply it to a real project with a thinking partner.