How to Run Quarterly Planning in Jira (Step-by-Step)
Jira Advanced Roadmaps provides initiative-level planning, cross-team capacity management, and dependency tracking for quarterly planning.
Use Jira initiatives as the quarterly planning unit and Advanced Roadmaps for capacity allocation.
Step-by-step guide
Step 1: Create quarterly initiatives
Initiatives contain Epics, which contain Stories. Name with the quarter: "Q3-2026: Self-serve onboarding."
Step 2: Configure Advanced Roadmaps capacity
Add teams, set weekly story point capacity, account for time off. Roadmaps uses capacity to auto-schedule and flag over-commitment.
Step 3: Map cross-team dependencies
Create dependency lines between epics across teams. Red lines indicate scheduling conflicts.
Step 4: Run the planning session
Walk through: Initiatives, capacity per team, cross-team dependencies, and risks.
Step 5: Track quarterly progress
Dashboard with: initiative status pie chart, velocity per team, dependency status, and burndown by initiative.
Common mistakes
No capacity configuration
Without capacity, Advanced Roadmaps is just a timeline. The value is in auto-scheduling based on team capacity.
Too many initiatives
Each team should own 1-3 initiatives per quarter.
Planning at story level
Quarterly planning is initiative and epic level. Stories are sprint-level.
Tips
- Export the plan as a Confluence page for stakeholder communication
- Run a mid-quarter checkpoint
- Use Labels to tag initiatives by theme
How Vantage helps
Vantage generates PRDs and tickets that map to Jira initiatives and epics. When your quarterly plan includes a new initiative, Vantage produces specifications and tickets that populate it with dependency-aware work items.