These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Portfolio Management
- Features
- Roadmaps and dependencies
Roadmaps and dependencies
Keep executive timing connected to delivery evidence and the dependencies between initiatives. Preserve each roadmap snapshot and its date. External project links supply context without importing unrelated task ownership. Missing delivery information stays visible as an exception.
OverviewRoadmap (Latest Snapshot)×
Portfolio Management · Roadmaps and dependencies
New
Roadmap (Latest Snapshot)
Roadmap timeline
| Initiative | Start date | Target end date | Current stage | Health score | Percent complete | |
|---|---|---|---|---|---|---|
| Returns process simplification | 21 Oct | 28 Oct | Idea screening | Green | 87 | |
| Supplier data consolidation | 13 Oct | 15 Oct | Discovery approval | Amber | 68 | |
| Field technician mobility | 15 Oct | 19 Oct | Business case review | Red | 92 | |
| Customer onboarding redesign | 04 Nov | 11 Nov | Funding approval | Green | 95 | |
| Supplier data consolidation | 13 Oct | 17 Oct | Pilot readiness | Amber | 62 |
6 of 6 records
Idea screeningRoadmap timeline · RT-12789
GreenInitiativeReturns process simplification
Start date21 Oct
Target end date28 Oct
Percent complete87
What you can do
Delivery linkage and roadmap
As the Initiative is delivered, initiative projects line items link to delivering Projects in pm-projects (one or several project refs). The roadmap-recompute workflow (the configured schedule weekly Sunday 22:00) reads each initiative projects’ linked Project status, %complete, and end-date drift; freezes a roadmap snapshots row per Portfolio with roadmap timeline line items per Initiative capturing start date, target end date, current stage, health score, and percent complete. The Roadmap (Latest Snapshot) view renders the timeline-bar grid; the Roadmap Drift report compares snapshot-over-snapshot to surface systemic slip.
Risk and dependency surfacing
Initiative Owner raises Risks (Likelihood × Impact, Mitigation, Owner) and Dependencies (Upstream ↔ Downstream Initiative, Type, need by date). The dependency-risk-detector workflow (nightly 04:00) joins each open Dependency to the upstream Initiative’s health score and baseline-drift, flags any where the upstream is Amber / Red as risk flag: At risk, and emails the downstream Initiative Owner + portfolio manager with the impact summary. Open Risks Heatmap is the working view; the rolled-up at-risk count feeds the Portfolio Health Dashboard.
Understand a slipping dependency
Suppose a downstream initiative needs a deliverable from another initiative before its next gate. Record the upstream and downstream references, the need date and the dependency type. If the upstream delivery observation slips, show the exposure to the downstream owner with its source and snapshot date. A risk flag helps the program manager coordinate a response; it does not authorize a new budget or change the downstream gate policy.
Both initiative references must be within the permitted workspace and program context. Where a user can see only one side of the relationship, reports must preserve the corresponding visibility rules. An executive summary can show the aggregate exposure without disclosing a restricted risk narrative.
Compare observations across time
Keep roadmap snapshots and their roadmap timeline records unchanged after capture. Compare the current target date with the earlier observation to explain drift. If the project feed is unavailable, distinguish stale or unknown evidence from an on-track result. Preserve the authorized project ref mapping and the last successful refresh. When a project is replaced, retain the old linkage history so the next portfolio review can explain why the roadmap changed.
What your team sees
- Roadmap (Latest Snapshot) — Compare initiative dates and dependency context from the latest dated snapshot.
What it keeps track of
Data model- Initiatives
- A discrete strategic bet that the Portfolio is funding — the Portfolio-level unit. Carries the benefit case, the current stage gate, the alignment score, the KPI rollup, and the delivering Projects. Promoted from a Proposal or stood up directly by a Portfolio Manager.
- Initiative projects
- The bridge to pm-projects. One row per delivering Project. A single Initiative can be delivered by one Project or by several; a Project belongs to one Initiative. The roadmap-recompute and KPI-rollup jobs read the linked Project for status, %complete, and end-date drift.
- Roadmap snapshots
- Frozen point-in-time snapshots of the portfolio roadmap. Generated weekly by roadmap-recompute. Snapshot-over-snapshot diffs power the Roadmap Drift report.
- Roadmap timeline
- One row per Initiative captured in a roadmap snapshot. The timeline-bar grid view reads this table to render the roadmap chart for any historical snapshot.
- Risks
- Risks per Initiative. Likelihood × Impact composite drives the Risk heatmap on the Portfolio dashboard. Mitigation owner is named; status walks Open → Mitigating → Closed / Realized.
- Dependencies
- Cross-Initiative dependencies. The dependency-risk-detector nightly job flags rows where the upstream Initiative is Amber / Red or behind baseline as a downstream risk.
Who uses it
Permissions- Program Manager
- Owns cross-initiative dependencies.
- Initiative Owner
- Maintains risks.
- Project Manager
- Supplies permitted delivery context.
Set up Portfolio Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.