Forem

Thesius Code
Thesius Code

Posted on • Originally published at datanest-stores.pages.dev

Roadmap Planning System

#projectmanagement #agile #productivity #leadership

Roadmap Planning System

A complete roadmap planning toolkit with quarterly and annual planning templates, prioritization frameworks (RICE, ICE, MoSCoW), capacity planning tools, and stakeholder presentation formats.

Key Features

  • Quarterly Roadmap Template — Theme-based planning with clear commitments vs. explorations
  • Annual Strategic Roadmap — Year-level vision with quarterly milestones
  • RICE Prioritization Framework — Reach, Impact, Confidence, Effort scoring with calculator
  • ICE Scoring Model — Impact, Confidence, Ease for rapid prioritization
  • MoSCoW Classification — Must-have, Should-have, Could-have, Won't-have categorization
  • Capacity Planning — Team capacity calculator with allocation tracking
  • Stakeholder Views — Different roadmap views for executives, engineering, and customers

What's Included

File Purpose
templates/quarterly-roadmap.md Quarter-level planning template
templates/annual-roadmap.md Annual strategic roadmap
templates/rice-prioritization.md RICE scoring framework and calculator
templates/ice-scoring.md ICE rapid prioritization template
templates/moscow-classification.md MoSCoW requirement categorization
templates/capacity-planning.md Team capacity and allocation tracker
templates/roadmap-exec-view.md Executive-level roadmap presentation
templates/roadmap-eng-view.md Engineering-focused roadmap detail
docs/overview.md Planning methodology guide
config.example.yaml Planning cadence and framework defaults

Quick Start

  1. Start with templates/annual-roadmap.md to define your yearly themes and bets
  2. Break the current quarter into initiatives using templates/quarterly-roadmap.md
  3. Prioritize your backlog using RICE (templates/rice-prioritization.md)
  4. Validate capacity with templates/capacity-planning.md
  5. Create stakeholder views for your next roadmap review

Template Examples

RICE Prioritization Matrix 

Initiative          | Reach   | Impact | Confidence | Effort  | RICE Score
--------------------|---------|--------|------------|---------|----------
Onboarding redesign | 5,000/q | 3 (high)| 80%       | 3 eng-mo| 4,000
API v2 launch       | 800/q   | 3 (high)| 90%       | 6 eng-mo| 360
Dark mode           | 12,000/q| 1 (low) | 95%       | 1 eng-mo| 11,400
SSO integration     | 200/q   | 3 (high)| 70%       | 2 eng-mo| 210
Mobile push notifs  | 8,000/q | 2 (med) | 60%       | 2 eng-mo| 4,800

Score = (Reach x Impact x Confidence) / Effort

Priority order: Dark mode > Mobile push > Onboarding > API v2 > SSO
Note: RICE is a starting point, not the final answer. Apply judgment.
Enter fullscreen mode Exit fullscreen mode

MoSCoW Classification 

MUST HAVE (launch blockers — non-negotiable):
  - [ ] User authentication and authorization
  - [ ] Payment processing with error handling
  - [ ] Core workflow: create, edit, delete

SHOULD HAVE (important but launch is viable without them):
  - [ ] Email notifications for key events
  - [ ] Export to CSV functionality
  - [ ] Search and filtering

COULD HAVE (nice-to-have if time permits):
  - [ ] Dark mode theme
  - [ ] Keyboard shortcuts
  - [ ] Bulk operations

WON'T HAVE (explicitly deferred — not this release):
  - [ ] Mobile app
  - [ ] Third-party integrations
  - [ ] Multi-language support
Enter fullscreen mode Exit fullscreen mode

Quarterly Roadmap Structure 

Q3 2026 Roadmap — Theme: "Reduce Time-to-Value"

COMMITTED (high confidence, resources allocated):
  1. Onboarding redesign       | 3 engineers | Jul-Aug  | KR: TTFV < 1 day
  2. In-app help system        | 1 engineer  | Jul      | KR: Support tickets -20%
  3. Template library           | 2 engineers | Aug-Sep  | KR: Activation +15%

PLANNED (medium confidence, pending capacity):
  4. API documentation overhaul | 1 engineer  | Sep      | KR: API adoption +25%
  5. Mobile responsive fixes    | 1 engineer  | Aug      | KR: Mobile bounce -30%

EXPLORING (low confidence, needs discovery):
  6. AI-assisted onboarding     | Discovery   | Q3       | Decision point: end of Aug
  7. Partner integrations       | Research    | Q3       | Decision point: mid Sep
Enter fullscreen mode Exit fullscreen mode

Usage Guide

  1. Annual Planning (December): Set 3-5 strategic themes for the year. Each theme should map to a company OKR. Don't over-commit at this level.
  2. Quarterly Planning (month before quarter): Break themes into initiatives. Prioritize with RICE. Validate capacity. Classify with MoSCoW.
  3. Monthly Check-ins: Review progress against quarterly commitments. Adjust PLANNED items if capacity changes. Move EXPLORING items to PLANNED when discovery is complete.
  4. Stakeholder Reviews: Use exec view for leadership (themes + outcomes). Use eng view for technical teams (details + dependencies).

Best Practices

  • Separate commitments from aspirations — use Committed / Planned / Exploring tiers to set honest expectations
  • Time-bound everything — "Q3" is better than "H2"; "July" is better than "Q3"
  • Prioritize outcomes over features — "Reduce churn by 10%" is better than "Build feature X"
  • Revisit quarterly — a roadmap that never changes is either perfect or ignored
  • Show what you're NOT doing — a roadmap without trade-offs is a wish list
  • Version and date every share — stakeholders will reference outdated versions; make it easy to check currency

This is 1 of 11 resources in the PM Toolkit Pro toolkit. Get the complete [Roadmap Planning System] with all files, templates, and documentation for $39.

Get the Full Kit →

Or grab the entire PM Toolkit Pro bundle (11 products) for $129 — save 30%.

Get the Complete Bundle →

Related Articles

Top comments (0)