Work · Use case

A project that is running late, brought to acceptance.

A typical project recovery engagement. The project is under way, with a specification, vendors and a plan, but it is not progressing at the pace you need.

Your project is under way, but not moving

Milestones slip from one status meeting to the next. Vendors deliver late, or deliver something other than what was ordered. Nobody can say with confidence what is finished, what is open and when acceptance will come. The specification exists, but the project is no longer measured against it.

Typical situation

  • Slipping milestones, no agreed recovery date
  • Deliverables disputed between you and the vendor
  • Status reports without evidence behind them

We assess and propose a way to acceptance. You decide.

We read the requirements specification (Lastenheft), the contracts and the deliverables received so far, and check them against each other and against what is actually running. We review the deployment plan and the open issues with your team and with the vendors. The result is a findings report, a reworked deployment plan with a new timeline, and a list of what each vendor still owes.

Deliverables

  • Findings: specification against deliverables against the system
  • Reworked deployment plan and timeline
  • Open items and vendor obligations, with dates

We fix what blocks progress and set up the tooling to run the project

We resolve the technical issues that hold the project up, together with your team and the vendors. Alongside, we set up the project management tooling: a deliverables register tied to the specification, acceptance criteria for each deliverable, an issue and decision log, and reporting that shows progress from evidence rather than from status slides. Vendors are held to what they signed, in writing and with dates.

Components

  • Deliverables register with acceptance criteria
  • Issue, risk and decision log
  • Progress reporting from evidence

Together we run it to acceptance

We run the project with you against the new plan: weekly reviews on evidence, vendor meetings with the obligations list on the table, and an acceptance test for each deliverable as it arrives. Where a vendor cannot deliver, we say so early and propose the alternative.

Typical work

  • Weekly reviews and vendor meetings
  • Acceptance tests per deliverable
  • Escalations backed by evidence

You own the result

The project reaches acceptance, and the tooling that got it there stays with you: the deliverables register, the logs, the reports and the method behind them, documented so your team runs the next project the same way.

You receive

  • Accepted project, with the acceptance records
  • All project management and reporting tooling
  • Documented method for the next project

A project that is not moving? Tell us the problem.

Contact us