User Guide & Documentation
Everything you need to know to master Roadmap Planner and create effective quarterly roadmaps.
📑 Table of Contents
🚀 Getting Started
Roadmap Planner is a free, privacy-first tool for creating quarterly roadmaps and Gantt charts directly in your browser. No login required, no data stored on servers.
Quick Start Guide
- Open the app: Visit my.roadmapplanner.app
- Add a project: Enter project name and priority (1-5)
- Add subprojects: Break down your project into logical groups
- Add features: Define specific deliverables with effort estimates
- View Gantt chart: Click "Show Gantt" to visualize your roadmap
- Export your work: Click "Export CSV" to save locally
🏗️ Understanding Project Structure
Roadmap Planner uses a 3-level hierarchy to organize your work:
1. Projects (Top Level)
The highest level containers representing major initiatives or product areas.
- Example: "AI Copilot 2026", "Mobile App Redesign", "Backend Infrastructure"
- Properties: Name, Priority (1-5)
- Projects appear as colored bars in the Gantt chart
2. Subprojects (Middle Level)
Logical groupings within a project. Each subproject belongs to exactly one project.
- Example: Within "AI Copilot 2026" → "Backend Architecture", "UI Components", "Training Pipeline"
- Properties: Name, Parent Project, Priority (1-5)
- Helps organize features into workstreams
3. Features (Bottom Level)
Individual deliverable items. Each feature belongs to one subproject (and therefore one project).
- Example: "User Authentication API", "Real-time Collaboration", "Data Export Module"
- Properties: Name, Description, Priority (1-5), Effort (story points), Quarter (Q1-Q4)
- The actual work items that will be tracked and delivered
📊 Example Hierarchy
Project: AI Copilot 2026 (Priority: 1)
├─ Subproject: Backend Architecture (Priority: 2)
│ ├─ Feature: API Gateway v2 (Priority: 1, Effort: 13, Q1)
│ ├─ Feature: Database Optimization (Priority: 2, Effort: 8, Q1)
│ └─ Feature: Caching Layer (Priority: 3, Effort: 5, Q2)
└─ Subproject: UI Components (Priority: 1)
├─ Feature: Chat Interface (Priority: 1, Effort: 21, Q1)
└─ Feature: Code Editor Integration (Priority: 2, Effort: 13, Q2)
📅 Time Unit Planning (NEW)
Roadmap Planner now supports flexible time unit planning, allowing you to plan in quarters, months, weeks, or days depending on your project needs.
Available Time Units
| Time Unit | Periods | Best For |
|---|---|---|
| Quarters | Q1, Q2, Q3, Q4 | Strategic planning, annual roadmaps, executive-level views |
| Months | Jan - Dec (M1 - M12) | Product launches, marketing campaigns, medium-term planning |
| Weeks | Week 1 - 52 | Sprint planning, short-term deliverables, agile workflows |
| Days | Day 1 - 365 | Event planning, launch schedules, detailed timelines |
How to Switch Time Units
- Locate the "Time Unit" dropdown in the actions bar (above the table)
- Select your desired time unit (Quarters, Months, Weeks, or Days)
- The Gantt chart and delivery columns will automatically update to show the new time scale
- Existing period assignments are automatically converted (e.g., Q1 → Jan-Mar)
Automatic Period Conversion
When you change time units, the app intelligently converts your existing assignments:
- Q1 (Quarter) → Jan, Feb, Mar (Months) → Weeks 1-13 → Days 1-90
- Q2 → Apr, May, Jun → Weeks 14-26 → Days 91-181
- Q3 → Jul, Aug, Sep → Weeks 27-39 → Days 182-273
- Q4 → Oct, Nov, Dec → Weeks 40-52 → Days 274-365
📊 Example Use Case
You're planning a product launch:
- Quarters view: See that "Mobile App 2.0" spans Q2-Q3
- Switch to Months: See it spans Apr-Aug for budgeting discussions
- Switch to Weeks: Break down features into 2-week sprint cycles
- Switch to Days: Plan the final launch week day-by-day
🎯 Multi-Period Selection (NEW)
Features can now span multiple periods, allowing you to represent work that takes longer than a single quarter, month, or week.
How to Select Multiple Periods
- When adding or editing a feature, find the "Delivery (Period)" dropdown
- Hold
Ctrl(Windows/Linux) orCmd(Mac) while clicking - Select multiple periods (e.g., Q1, Q2, Q3)
- The feature will span all selected periods in the Gantt chart
When to Use Multi-Period Selection
- Long-running features: Infrastructure projects, major refactors, multi-phase rollouts
- Continuous work: Ongoing maintenance, support, research activities
- Phased deliveries: Beta (Q1) → Pilot (Q2) → General Availability (Q3)
- Cross-quarter dependencies: Features that block or enable other work over multiple periods
📊 Example
Feature: "Complete Backend Rewrite"
- Priority: 1 (Critical)
- Effort: 89 points
- Delivery: Q1, Q2, Q3 (selected via Ctrl+Click)
- Result: Gantt chart shows a continuous bar spanning 3 quarters
Visual Representation
In the Gantt chart:
- Single period: Shows as a bar within one column (e.g., just Q1)
- Multiple periods: Shows as a continuous bar spanning multiple columns (e.g., Q1-Q2-Q3)
- Color coding: Bar color matches the parent project
Combining with Time Units
Multi-period selection works seamlessly with time unit switching:
- Select Q1-Q2 in Quarters view → automatically becomes Jan-Jun in Months view
- Select Weeks 10-15 in Weeks view → automatically becomes Mar-Apr in Months view
- Conversions preserve the span and relative positioning of your features
🎯 Prioritization System
Roadmap Planner uses an automatic prioritization algorithm to rank features and assign them to quarters.
Priority Scale (1-5)
Lower numbers = higher priority. Each level (project, subproject, feature) has its own priority:
| Priority | Meaning | When to Use |
|---|---|---|
| 1 | Critical | Must-have, blocking other work, top business priority |
| 2 | High | Important features, core functionality |
| 3 | Medium | Standard features, typical priority |
| 4 | Low | Nice-to-have, can be deferred |
| 5 | Very Low | Future consideration, experimental |
Composite Score Calculation
Features are automatically ranked using this formula:
Score = Project Priority + Subproject Priority + Feature Priority + Effort Weight
Effort Weight is calculated as: Math.ceil(effort / 10)
- Lower scores rank higher (scheduled earlier)
- Larger effort = slightly lower ranking (assumes longer tasks should start earlier)
- This creates a balanced distribution across Q1-Q4
Automatic Quarter Assignment
After scoring, features are distributed:
- Top 25% → Q1
- 25-50% → Q2
- 50-75% → Q3
- Bottom 25% → Q4
➕ Adding Projects, Subprojects & Features
Adding a Project
- Find the "1. New Project" section in the left panel
- Enter project name (e.g., "Mobile App 2026")
- Set priority (1-5, default is 3)
- Click "Add Project" button
Adding a Subproject
- Find the "2. New Subproject" section
- Select the parent project from dropdown
- Enter subproject name (e.g., "Authentication System")
- Set priority (1-5)
- Click "Add Subproject" button
Adding a Feature
- Find the "3. New Feature" section
- Select project from first dropdown
- Select subproject from second dropdown (updates based on project)
- Enter feature name
- (Optional) Add description for hover tooltip
- Set priority (1-5)
- Set effort in story points (e.g., 1, 2, 3, 5, 8, 13, 21)
- (Optional) Set specific quarter or leave blank for automatic
- Click "Add Feature" button
💼 Example: Planning a Mobile App
Project: Mobile App Redesign (Priority: 1)
Subproject: User Experience (Priority: 1)
Feature:
- Name: "Onboarding Flow Redesign"
- Description: "New 3-step onboarding with personalization"
- Priority: 1
- Effort: 13 points
- Quarter: Q1 (or leave blank for auto-assignment)
📊 Using the Gantt Chart
The Gantt chart provides a visual timeline of your roadmap across Q1-Q4.
Viewing the Gantt Chart
- Mini preview: Visible in the main app below the table
- Full-screen mode: Click "Open Gantt (popup)" button to open in new window
Understanding the Chart
- Rows: Each row represents a project
- Colored bars: Show which quarters have features scheduled
- Bar position: Aligned to Q1, Q2, Q3, Q4 columns
- Bar width: Spans single or multiple quarters if features cross quarters
- Colors: Each project gets a unique color from predefined palette
Gantt Chart Legend
| Element | Description |
|---|---|
| Q1 Column | January - March |
| Q2 Column | April - June |
| Q3 Column | July - September |
| Q4 Column | October - December |
💾 CSV Import & Export
Since Roadmap Planner doesn't store data on servers, CSV export is your primary save mechanism.
Exporting to CSV
- Click the "Export CSV" button in the app
- A file named
roadmap_export.csvwill download - This file contains all projects, subprojects, and features
- Can be opened in Excel, Google Sheets, or any text editor
CSV File Structure
The exported CSV contains these columns:
Type- "project", "subproject", or "feature"ID- Unique identifier (p1, s1, f1, etc.)Name- Item namePriority- 1-5 valueParentID- Links subprojects to projects, features to subprojectsEffort- Story points (features only)Quarter- Q1, Q2, Q3, Q4, or rangesDescription- Optional description text
Importing from CSV
- Click the "Import CSV" button
- Select your previously exported CSV file (or create one following the structure)
- The app will parse and load all items
- Warning: Importing replaces all current data. Export first if needed!
Editing CSV in Excel/Sheets
You can bulk-edit your roadmap:
- Export CSV from the app
- Open in Excel or Google Sheets
- Edit priorities, efforts, quarters, add/remove features
- Save as CSV (not XLSX)
- Import back into the app
🖱️ Drag & Drop Reordering
You can manually reorder features by dragging rows in the table.
How to Use Drag & Drop
- Make sure you're in "Features" view mode (default)
- Click and hold on any feature row
- Drag the row up or down
- Release to drop in new position
- The app will automatically recalculate priorities based on new order
Priority Recalculation
After dropping a row, the app assigns new priorities:
- Top 20% of features → Priority 1
- 20-40% → Priority 2
- 40-60% → Priority 3
- 60-80% → Priority 4
- Bottom 20% → Priority 5
Limitations
- Only works in Features view mode (not in Subprojects or Projects aggregation views)
- Changes are lost on page refresh unless you export CSV
- Drag & drop overrides automatic priority scoring
👁️ View Modes
Switch between 3 different aggregation levels to see your roadmap at different granularities.
1. Features View (Default)
- Shows individual features as separate rows
- Most detailed view
- Enables drag & drop reordering
- Best for day-to-day planning and feature management
2. Subprojects View
- Groups features by subproject
- Shows aggregated effort (sum of all features in subproject)
- Shows averaged score
- Shows quarter span (earliest to latest feature quarter)
- Good for workstream-level planning
3. Projects View
- Groups features by project (top level)
- Shows total effort across entire project
- Shows averaged score
- Shows full quarter span
- Best for executive summaries and high-level roadmaps
Switching Views
Use the view mode selector (usually radio buttons or dropdown) to switch between modes. The table and Gantt chart will update automatically.
📈 View Mode Comparison
Features View: 15 individual features listed
Subprojects View: 5 subprojects, each showing total effort (sum of 3 features each)
Projects View: 2 projects, each showing total effort (sum of all features)
💼 Use Cases & Examples
Use Case 1: Startup Annual Planning
Scenario: A SaaS startup needs to plan 2026 product development
- Create 3 projects: "Core Platform", "Mobile App", "Enterprise Features"
- Break each into subprojects (e.g., Core Platform → Backend, Frontend, API)
- Add all feature ideas with rough effort estimates
- Let automatic prioritization assign quarters
- Review Gantt chart with team
- Manually drag high-priority features to Q1
- Export CSV and share with stakeholders
- Re-import monthly to track progress and adjust
Use Case 2: Product Manager Quarterly OKRs
Scenario: PM needs to align features with quarterly OKRs
- Create one project per OKR objective
- Add subprojects for key results
- Add features as initiatives supporting each key result
- Set priorities based on OKR weights
- Set effort based on team capacity (velocity)
- View in Projects mode to see OKR-level summary
- Export for quarterly review presentations
Use Case 3: Dev Team Sprint Planning
Scenario: Engineering team converting backlog to quarterly sprints
- Import existing backlog from CSV (exported from Jira/Linear)
- Group tickets into logical subprojects (epics)
- Assign story point efforts
- Set priorities based on business value
- Let automatic quarter assignment distribute work
- Drag & drop to fine-tune sprint assignments
- Use Gantt chart in standups to show progress
Use Case 4: Freelancer Client Projects
Scenario: Freelancer managing multiple client deliverables
- Create one project per client
- Add subprojects for each engagement/contract
- Add features as specific deliverables
- Set effort in estimated hours (convert to points)
- View Gantt to identify capacity conflicts
- Export CSV to send timeline to clients
No results found
Try different keywords or clear your search.