Back to the Playbook
DefineDE-15
Review the roadmap
Check the roadmap against progress in Jira, the code and the objectives, flag where plan and reality drift apart, and decide adjustments with stakeholders.
Product statusAvailable now
Context in5 required inputsCurrent roadmap · Product objectives · Epic progress in Jira
TransformationHead of Product + Product Agent + Architecture AgentAtlassian · Code Analysis · Local Files · Estimate Feature
OutcomeRoadmap review with drift flags, decisions and the updated roadmap.Artifact: Roadmap
Why it matters
A roadmap anchored in Jira and code: every initiative shows why it exists, what it depends on and how far it really is, so the review is about decisions, not about collecting status.
Owner
Head of Product
Human-led
Participants · Agents
Product ManagerEngineerProduct AgentArchitecture Agent
Trigger
A monthly or quarterly roadmap review, or a material change in objectives or capacity.
Required context
Product BrainCurrent roadmapProduct BrainProduct objectivesJiraEpic progress in JiraCodeDelivery reality from branches and pull requestsArchitectureDependencies
Optional context
Product BrainOutcome reviewsCustomer evidenceCustomer evidenceFilesCapacity and hiring plans
Skills
AtlassianCode AnalysisLocal FilesEstimate Feature
Activity steps
- 1Compare each initiative's plan with its progress in Jira and the code.
- 2Flag drift in scope, dependencies, dates and objectives.
- 3Prepare the decisions the review needs, with options.
- 4Decide the adjustments and record them.
- 5Update the roadmap and inform the affected teams.
Output
Roadmap review with drift flags, decisions and the updated roadmap.
Artifacts
Updates: Roadmap, Decision record, Product Brain
What good looks like
- Progress comes from Jira and the code, not from status reports.
- Every drift flag names its cause.
- Decisions are recorded with rationale.
- The roadmap after the review matches the objectives.
Quality gate
Product leadership approves roadmap changes.
Destination
RoadmapProduct BrainJira
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.