Two-way sync with Azure DevOps, Jira, Microsoft Project, Planner, Project for the Web, Smartsheet and Monday.com, plus Microsoft 365 and Okta SSO, Teams and Power BI. Delivery teams keep their tools; the portfolio assembles itself.
Capture requests against business challenges and score them against criteria the business helped set, with a published value range on every factor. “Why not mine?” gets answered with a model rather than a rank, and ideas that survive become projects in the same system. Migration from Project Online and Planner is automated and included, so the backlog you already have comes with you.
One resource pool with per-person work weeks and calendar exceptions, allocation in hours or % FTE, and over-allocation flagged in red, with amber for the person who is fine overall but breaches on a handful of dates. That amber case is what turns into a missed date.
Every quarter turns on questions nobody can answer defensibly. What comes out if the budget lands 15% lower? Which twenty of these forty requests should we take? Today those answers come from a spreadsheet one analyst owns: invisible to everyone else, stale the day after it is built, and impossible to defend when a business sponsor asks why their request was declined.
.jpg)
Streamline Project Portfolio Management and Visibility at Scale
Integrations
Capture new project request, streamline evaluation and prioritization
Product
Structured Approach for prioritizing and aligning portfolios with strategic priorities and resource constraints
Product
Last updated 20 August 2026
IT portfolio management, answered.
IT portfolio management covers everything IT owns and spends on: projects, applications, infrastructure, run cost. It asks how that whole estate should be funded. Project portfolio management is the narrower question of which change initiatives get approved, sequenced and staffed. PPM Express works on the change side, giving IT one ranked, capacity-checked view of the work it has agreed to take on.
Capturing every request the business makes of IT, assessing it consistently, and deciding what enters the delivery pipeline. It breaks in three predictable places: intake people route around, assessment that varies by assessor, and decisions that never reach the delivery teams. PPM Express addresses the last two, with one scoring model applied to all demand and approved decisions published back into the tools that deliver.
Few, weighted, and written down. Most IT portfolios need strategic contribution, financial return, risk or compliance exposure, and delivery effort, each with a published scale so different assessors produce comparable numbers. PPM Express lets you build that as weighted strategic and risk factors. For lighter calls you can use MoSCoW, ICE, RICE, WSJF or value versus effort instead, or run two and see where they disagree.
Each project follows a process made of phases and stages, with a gate between stages. You decide which gates require sign-off. The project manager names one or more approvers, who review the request in the Approval Center and either approve or reject with a comment. Everyone has to approve for the project to advance. Reviewers typically look at business value, risk, schedule, budget, resources and what was actually delivered.
Less than you'd think, as long as everything lands on the same scorecard eventually. Demand gets assessed against the strategic and risk factors your governance agreed, each with a published value range. A request from a business unit that knows how to write a business case is then measured the same way as one scribbled in an email. Informal arrival, formal assessment.
Change what has to be argued. When rank comes from a published model, escalation stops paying off, because a stakeholder who wants to move up has to argue that the strategic weighting itself is wrong, in front of the peers who agreed it. Few people take that on. PPM Express also keeps the decision history, so "we agreed this in March" is checkable rather than contestable.
Service management platforms are built around tickets and service delivery. Portfolio decisions need money, capacity and strategic value in one view. PPM Express connects to Azure DevOps, Jira, Microsoft Project, Microsoft Planner, Smartsheet and Monday.com to assemble the delivery picture, and holds budget, forecast, benefits and resource plans alongside it. If your current platform already does portfolio scoring and capacity modeling well, you may not need both.
Test the plan against what people actually have left, not against headcount. PPM Express calculates capacity from each resource's work week and calendar exceptions, then shows allocation against it. Overallocation is flagged before IT commits. "We think we can absorb this" turns into a number the CIO can put in front of the business, which makes saying no defensible rather than political.
The Resources page and Resource Dashboard show planned, capacity, actual and availability figures for every person, viewable in hours, percent, FTE or chart form. Allocation within capacity shows green, a single overloaded day shows yellow, and genuine overallocation shows red. You can filter by role, department or skill, which is usually how you find the four people every plan quietly depends on.
That works, and it's a common reason enterprises buy PPM Express. Both are supported connections, alongside Microsoft Project, Microsoft Planner, Smartsheet and Monday.com, and work from all of them rolls into one portfolio. In organizations where a merger or plain team preference left two systems of record standing, you get the combined view without a migration and without maintaining a sync layer between the trackers.
Three variants are supported. Project Online and Project for the Web (Planner Premium) connect directly. For the Microsoft Project Desktop client, PPM Express Project Publisher is an add-in installed into Project itself, and your planners publish schedules up from the ribbon. Desktop 2016, 2019 and 2021 are supported. Azure DevOps Server, as distinct from Azure DevOps cloud, is not.
No. Connections are configured rather than built, and they read from tools you already run. There's no data model to design up front and no re-entry of existing projects. Financial data is cached and refreshed when a project actually changes, so a large estate stays quick without anyone owning a nightly batch job.
Microsoft 365 and Okta SSO for identity, so access follows the directory you already manage. Data residency in the US or the EU, full GDPR compliance, and custom DPAs where required. Strict tenant isolation between customers. Detailed audit logs covering changes to the portfolio of record, which is normally the first thing your security review and internal audit ask about.
.svg){kind=small}
