There are four status colors in Planview’s portfolio roll-up. Three of them are the ones you expect. The fourth is gray, and it means the project manager did not report (their documentation, plainly).
That gray ball is the most honest object in enterprise portfolio management, and it is worth sitting with. It exists because the color is an opinion somebody has to remember to have. Green does not arrive from anywhere. It arrives from a person, on a Thursday, in a form — and when the person is busy, the system needs a way to say so.
Planview brings a mature strategic portfolio suite, and the record supports that position: a Gartner Leader in strategic portfolio management, and since its acquisition of Sciforma in February 2025 the owner of two of the ten incumbents we measure against. Investment and Capacity Planning gives a portfolio director four working views — Rank, Analyze, Shift and Balance — and lets a chosen scenario be published as the plan of record. Capacity targets are time-phased at any level of the organization. Financials carry an explicit capital-versus-operating split. Hub moves work items across sixty-plus tools, bi-directionally, including GitHub and GitLab. That breadth serves established portfolio operations. SprintLoop differentiates at the evidence and acceptance layer.
Here is the argument anyway. Every one of those capabilities takes its input from testimony, and testimony is the thing a delivery organization staffed with agents can no longer supply.
What Planview shipped when the shape changed
Copilot reached general availability in the November 2024 release with status summarization, risk flagging and questions over metrics. Then came Sentiment Analysis: software that judges whether work is on track by reading the emotional tone of comment and status text.
It is a well-built instrument for interviewing humans, delivered at the moment the interview stopped returning signal. You cannot sentiment-analyze an agent. It has no tone. And the humans still in the loop are not a reliable fallback either — in METR’s controlled trial, experienced developers working in their own repositories were 19% slower with AI tools while believing they had been 20% faster. That is not a story about careless engineers. It is a measurement of self-report and reality coming apart under exactly the conditions every enterprise is now creating deliberately.
So the question a portfolio tool has to answer moves. Not what did the project manager say, but what happened, and who accepted it.
What we built instead
A requirement carries its citations. The citations resolve against one pinned commit — a forty-character hash, not “the repository” — and a test result binds the requirement at the rung the evidence actually supports. A skipped test binds nothing. A failing test still binds, at its rung, with the failure as its outcome, because this is a record rather than a dashboard. The top rungs on the ladder are reached only by evidence that actually exists — nothing is approximated upward, which is the whole point of having rungs.
Then a named human accepts. Not as a policy: acceptance is recorded against the signed-in person, taken from their session rather than from anything the request carries, so a submission naming somebody else is refused instead of trusted. An agent has no identity to be recorded as, and cannot obtain one.
The objection worth taking seriously
The easy version is that this is a dashboard with better vocabulary. The test that settles it is about inputs. A dashboard’s inputs are things people typed: the color they chose, the percent they estimated, the comment a model scored for tone. Ours are things that happened. You can rebuild any dashboard from our rows. You cannot rebuild our rows from a dashboard, because it never held them.
The harder version is commercial: Planview can add commit-level binding next year and keep everything else it has. Maybe. But most of what we built is refusals, and refusals are expensive to retrofit onto an installed base. A vendor whose roll-up ships a gray ball for “nobody reported” would have to take the gray ball away to ship this, and the gray ball is there because thousands of customers need it on a Thursday afternoon.
Where Planview wins
Resource capacity in Planview is time-phased across the organization; SprintLoop records named capacity, allocation and workload decisions. Planview can publish a selected scenario as the plan of record; SprintLoop compares named, versioned assumptions against recorded funding, allocations, benefits and dependency contracts without declaring an automated winner. Planview Hub offers sixty-plus bidirectional integrations; SprintLoop currently focuses on repository, test, document and evidence workflows. Timesheets remain outside SprintLoop’s current scope. Buyers should weigh those breadth differences against the traceability and acceptance model described here.
Choose Planview Portfolios if…
Choose Planview if the portfolio office’s core job is brokering people and money across a large human delivery estate — if the question that keeps coming back is which of forty proposals can be staffed next quarter, and the answer has to survive a capacity model, a funding envelope and a published plan of record. That is what Investment and Capacity Planning is designed for; SprintLoop addresses a different control layer.
Choose it also when prebuilt integration breadth and established PPM operating patterns are decisive. Choose SprintLoop when requirements, delivery evidence and named acceptance need to remain connected at the pinned source and test level.
Come here instead if the delivery organization under the portfolio is getting smaller and more machine-produced, and the question you cannot answer any more is which requirement a build was made against and who accepted the result. The receipt verifies without an account, which is the fastest way to find out whether that is your problem.