Stalled platform projects re-baselined with acceptance criteria, then delivered
None of this is unusual. It is what a stalled build looks like from the inside.
A stalled project re-baselined against written acceptance criteria, then delivered to a stable release.
We review the codebase, the defect list and the delivery history to understand what state the project is actually in - not what the last status report said.
Every open issue is brought into one list, deduplicated and triaged, so there is a single source of truth instead of three trackers that disagree.
Each item on the list gets acceptance criteria you sign off before we build against it - so "fixed" means the same thing to everyone.
We work the scoped plan to a release that meets its criteria, with the business able to see progress against the list throughout.
Access to the codebase, the existing defect trackers and delivery history, and a short session with the outgoing team or vendor if one is available. From your side, a decision-maker who can sign off the re-baselined scope.
Every item carried into the delivery plan has its own written acceptance criteria, agreed before we build against it. "Done" is the release meeting those criteria, not a status update saying it's close.
2-week re-baseline, then scoped delivery
Rescue engagements are scoped from the findings of a Platform & Delivery-Risk Audit.