See which project needs a portfolio decision next.
Compare project updates, dependencies and capacity requests across a portfolio.
How to build your project portfolio tracker
Describe the job
Compare project updates, dependencies and capacity requests across a portfolio.
Review the first version
Choose how the project manager records the project and how the portfolio reviewer reviews the next step.
Refine the views
Ask First to adjust the fields and views for the people who will use the app.
Test before sharing
Walk through the process with a sample record and check who owns the next action.
Follow Portfolio PF-086 through the handoffs.
Inspect the inputs, review decision and unresolved exception in this fictional operating example.
Project portfolio tracker example
- Record
- Portfolio PF-086
- Review
- July portfolio
Current stage · Portfolio coordinator
Collect the project updates
A fictional coordinator collects weekly updates for a data migration and a customer launch in the same July review.
Read the full walkthrough
Collect the project updates
A fictional coordinator collects weekly updates for a data migration and a customer launch in the same July review.
- Record:
- Portfolio PF-086
- Review:
- July portfolio
Identify the shared dependency
Both project owners need the same reviewer during the same week. Their individual task boards do not settle that shared dependency.
- Record:
- Portfolio PF-086
- Project A:
- Data migration
Record the portfolio decision
The portfolio reviewer sequences the migration review first and requests a revised launch milestone from the second owner.
- Record:
- Portfolio PF-086
- Project B:
- Customer launch
Return the decision to the project owners
The revised milestone stays proposed until the project owner confirms it. The portfolio decision does not silently rewrite either project's task history.
- Record:
- Portfolio PF-086
- Dependency:
- Shared reviewer
What to include in your project portfolio tracker
Keep the project in context
Keep project, business owner, reporting period, milestone, dependency, capacity request, reported status and portfolio decision together so the next person can understand the request or record.
When the next step needs a decision
A sample coordinator collects weekly updates for a data migration and a customer launch in the same July review. Both project owners need the same reviewer during the same week. Their individual task boards do not settle that shared dependency.
Keep portfolio decision visible
Keep the resource constraint visible beside the reported project status.
Choose what each person needs
Give the project manager a working view and the portfolio reviewer a review view. Keep project and business owner attached to the decision as the work moves between them.
Questions about project portfolio tracker
Start with project, business owner, reporting period, milestone, dependency, capacity request, reported status and portfolio decision. Describe who enters the information and who reviews the next step.