Microsoft Project Roadmap: Build It in the Timeline View, Step by Step
9 min read ยท 2026-10-25
To make a Microsoft Project roadmap today, you build a high-level plan in Project desktop (one summary task per workstream, with key milestones under each), then show it in the Timeline view with one timeline bar per workstream and copy that timeline into PowerPoint. The separate Roadmap app that lived in Project for the web is gone: Microsoft retired Project for the web and the Roadmap app in August 2025 and points users to the Portfolios feature in the new Microsoft Planner instead.
The plan below takes six weeks, from choosing the right tool to running a steady update rhythm, with steps and a milestone you can check in each phase. After it you will find which Microsoft tool fits which need, exact build steps in Project desktop, a filled-in example for a CRM rollout program, who owns what, how to present the roadmap to leadership and how to keep it current with baselines. It is written for project managers, PMO leads and program managers who already plan in Project and need a view that executives will read.
The roadmap at a glance
Goal: By week 6, the program has one Project file with a baselined high-level plan, a timeline view with a bar per workstream, a monthly leadership slide made from it and a weekly update routine. Duration: 6 weeks
Choose the tool and scope (Week 1)
Decide where the roadmap lives and what it must show.
- Confirm which Project version your team has: Project desktop (Standard or Professional), the subscription desktop client, or Planner with premium plans.
- Agree with your sponsor on the audience, the time span and the level of detail, such as workstreams and milestones over 12 months.
- List the workstreams and the 10 to 20 milestones leadership cares about.
- Decide whether the roadmap covers one program or several projects, which changes the tool you need.
Milestone: A one-page brief approved by the sponsor naming the tool, audience, time span, workstreams and key milestones.
Structure the plan (Week 2)
Build the high-level plan that the roadmap view will draw from.
- Create one summary task per workstream and indent phases or deliverables under it.
- Add milestones as tasks with zero duration, named as results, such as Pilot sites live.
- Link dependencies between workstreams with predecessors, only where one truly waits on another.
- Add a custom text field for owner and one for roadmap status.
Milestone: A plan where every workstream has a summary task, every key milestone exists as a zero-duration task, and cross-workstream links are entered.
Build the timeline view (Week 3)
Turn the plan into a one-page visual roadmap.
- Turn on the Timeline from the View tab.
- Add one timeline bar per workstream with Format, Timeline Bar, and set each bar's date range.
- Add the summary tasks and milestones to the right bar, then drag them into rows.
- Show milestones as callouts and color each workstream with Background Color.
Milestone: A timeline that shows every workstream on its own bar with its milestones, readable at a glance on one screen.
Review and baseline (Week 4)
Get agreement on dates and lock a baseline to measure against.
- Walk each workstream lead through their bar and fix dates they cannot commit to.
- Review cross-workstream dependencies with all leads together.
- Set a baseline from the Project tab once the sponsor approves the dates.
- Save the file in a shared location the whole team can open.
Milestone: Dates agreed by every workstream lead, baseline set and approved by the sponsor.
Present to leadership (Week 5)
Turn the timeline into a slide leaders will read.
- Copy the timeline with Format, Copy Timeline, For Presentation and paste it into PowerPoint.
- Add three short lines beside it: progress since last month, top risks, decisions needed.
- Mark milestones that moved since the baseline in a different color.
- Present at the steering committee and record decisions.
Milestone: Roadmap slide presented at the steering committee, with decisions logged and owners named.
Run the update rhythm (Week 6)
Keep the roadmap current without a big effort each month.
- Ask workstream leads to update their tasks and status field every week before a set day.
- Check slipped milestones in the Tracking Gantt view against the baseline.
- Refresh the timeline slide monthly and keep last month's slide for comparison.
- Rebaseline only when the sponsor approves a scope or date change, and note why.
Milestone: One full update cycle completed on time by all workstream leads, and the next month's slide produced in under an hour.
Which Microsoft tool to use for a roadmap
Searchers often mean one of three things by a Microsoft Project roadmap, and the right answer depends on which. Microsoft Roadmap was an app that pulled projects from Project for the web, Project Online and Azure Boards into one view. Microsoft retired Project for the web and the Project and Roadmap apps in Teams in August 2025, and existing roadmaps were not moved over automatically. Microsoft also set the end of September 2026 as the retirement date for Project Online, and said Project desktop and Project Server are not affected.
Today, the most common options are below. Check with your Microsoft 365 admin which licenses you have before you choose, because features such as the Timeline and Portfolios in Planner depend on the plan.
- Project desktop (Standard, Professional or the subscription client): best for one program with dependencies and baselines. The roadmap is the Timeline view.
- Microsoft Planner with premium plans: has a Timeline view for each plan and a Portfolios feature that Microsoft offers in place of the old Roadmap. Portfolios do not connect to Azure DevOps or Project Online.
- Azure DevOps: for engineering teams who plan epics and features there, with Delivery Plans showing several teams on one timeline.
- PowerPoint: the final format for leadership, fed by a timeline copied from Project.
How to build the roadmap in Project desktop
Start from your high-level plan, not the detailed schedule. If you already have a detailed plan, create a separate roadmap file or use outline levels so the timeline shows only summary tasks and milestones. Use Task, Indent Task to place deliverables under each workstream summary task, and create milestones with the Milestone button on the Task tab or by entering a duration of zero.
Then build the view. On the View tab, check Timeline so it appears above the Gantt chart. Right-click each summary task or milestone you want in the task list and choose Add to Timeline. To get one bar per workstream, select the timeline and use Format, Timeline Bar, then open the new bar's shortcut menu and choose Date Range to set its span. Drag each task onto the bar for its workstream, and drag tasks up or down to stack them in rows. In the subscription desktop client, Format, Bar Label lets you name each bar after its workstream.
- Show key milestones as callouts: select one on the timeline and use Format, Display as Callout.
- Color by workstream: select tasks (hold Ctrl for several) and use Background Color on the Format tab.
- Simplify dates: use Format, Date Format to shorten or hide dates on bars.
- Add owner and status columns: use Project, Custom Fields to rename Text1 to Owner and Text2 to Status.
- Lock the plan: use Project, Set Baseline once dates are approved.
Example: a roadmap for a CRM rollout program
Picture a program manager running a CRM rollout for a sales team of 300 across three regions over nine months. The steering committee wants one view of the whole program each month. The Project file has four workstream summary tasks, and the timeline has four bars, one per workstream, each with its owner and milestones.
Notice the dependency between data and rollout. In the plan, the Region 1 go-live milestone has the data migration rehearsal as its predecessor, so a slip in data shows up on the rollout bar automatically.
- Configuration bar (owner: CRM solution architect): design sign-off in month 2, core build complete in month 4, integration with the quoting tool in month 5. Milestone shown as callout: system test passed.
- Data bar (owner: data lead): data cleanup in months 2-4, first migration rehearsal in month 5, final rehearsal in month 6. Milestone: rehearsal signed off by sales operations.
- Training and change bar (owner: change lead): champions named in month 3, train-the-trainer in month 6, regional training before each go-live. Milestone: all reps trained before their region goes live.
- Rollout bar (owner: program manager): Region 1 live in month 7, Region 2 in month 8, Region 3 in month 9. Milestone: legacy system switched to read-only.
Who owns what
One person owns the Project file and the roadmap view, usually the program manager or a PMO analyst. Workstream leads own the dates and status of their own tasks. Mixing the two, with everyone editing the timeline layout, makes the view fall apart in a few weeks.
Write the update routine into the program RACI so it does not depend on reminders. The roadmap is only as current as the slowest update.
- Sponsor: approves the baseline and any rebaseline, chairs the steering committee.
- Program manager: owns the file, the timeline layout and the monthly slide.
- Workstream leads: update their tasks and status weekly, flag risks to milestones.
- PMO analyst: checks updates, compares against baseline, prepares variance notes.
- Microsoft 365 admin: confirms licenses and access to Project or Planner premium features.
How to present it to leadership
Select the timeline, then use Format, Copy Timeline, For Presentation, which sizes the image for a PowerPoint slide. Paste it into a slide that uses the full width. Leaders read left to right, so add a thin today marker if your timeline does not show one, and place three short boxes underneath: what moved since last month, top three risks with owners, and decisions needed.
Leave out the Gantt chart, task-level dates and resource names. If leaders want detail, open the Project file and filter to one workstream. Use the same slide layout each month so they can compare at a glance, and keep the previous month's slide in the appendix.
Keeping the roadmap current
A roadmap that is three weeks old is worse than none, because people make decisions on it. Set a weekly update deadline for workstream leads, such as Thursday noon, and update the file yourself on Friday morning. Use the Tracking Gantt view from the Gantt Chart menu on the View tab to compare current dates with the baseline and see slips at once.
Rebaseline rarely. When the sponsor approves a real change in scope or dates, set a new baseline and write a short note explaining what changed and why. If you rebaseline every month, the baseline stops meaning anything and leadership loses sight of how far the program has moved.
Common mistakes to avoid
- Putting the detailed schedule on the timeline buries the story, so add only summary tasks and key milestones to the roadmap view.
- Drawing all workstreams on one timeline bar makes overlaps unreadable, so add one timeline bar per workstream and stack tasks in rows.
- Skipping the baseline means nobody can see what slipped, so set a baseline once the sponsor approves the dates.
- Rebuilding the roadmap slide by hand each month wastes hours and causes errors, so copy the timeline from Project with Copy Timeline every time.
- Letting every lead edit the timeline layout breaks the view, so give one person ownership of the layout and let leads update only their tasks.
- Planning around the retired Roadmap app wastes setup time, so confirm with your admin which Project or Planner licenses you have before you build.
Frequently asked questions
Does Microsoft Project have a roadmap view?
Project desktop has a Timeline view that works as a roadmap, with multiple timeline bars for workstreams and callouts for milestones. The separate Roadmap app in Project for the web was retired in August 2025. Microsoft now points to Portfolios in Planner for a cross-project view.
What replaced Microsoft Roadmap?
Microsoft offers the Portfolios feature in the new Microsoft Planner in place of Roadmap. Existing roadmaps were not migrated automatically and need to be recreated. Portfolios do not connect to Azure DevOps or Project Online, so engineering teams may use Delivery Plans in Azure DevOps instead.
How do I add multiple timelines in Microsoft Project?
Select the timeline, then use Format, Timeline Bar to add another bar. Open the new bar's shortcut menu and choose Date Range to set its dates. Drag tasks between bars to group them by workstream.
How do I put a Microsoft Project timeline into PowerPoint?
Select the timeline, go to the Format tab, choose Copy Timeline and then For Presentation. Paste it into your PowerPoint slide. The pasted timeline can be resized and formatted in PowerPoint.
Is Microsoft Project desktop being retired?
Microsoft's retirement notice covers Project Online, the cloud service, and states it does not affect Project desktop or Project Server. Check Microsoft's current lifecycle information for your specific version. Your Microsoft 365 admin can confirm which plans your organization has.