A team assembled around a defined outcome.
Bring together the delivery roles needed for a project, with milestones, governance and acceptance criteria agreed around the work.
What this covers.
A team assembled for a defined piece of work with a start, an end, milestones and acceptance criteria. The roles are chosen for the work rather than offered from a bench, and the team is sized to the plan rather than to a budget line.
How it runs.
Scope, milestones and acceptance criteria are agreed before mobilisation, along with what happens if the scope changes, because it usually does. Progress is measured against the milestones, and a slip is raised when it is visible rather than at the checkpoint.
Where it fits.
When the work has a definable end. If it does not, a standing team is a more honest arrangement and usually cheaper than a series of projects.
What you get, and what it depends on.
Defined deliverables against milestones, with a written change route and a planned demobilisation. It depends on the acceptance criteria being agreed before mobilisation rather than discussed at the end.
How we can work together
The model is chosen to suit the work, not to suit us. We will tell you when a fixed price is the wrong instrument.
Fixed scope
Defined deliverables and acceptance criteria, with a written change route.
Milestone based
Progress and payment tied to milestones that mean something, not to elapsed time.
Demobilisation planned
Handover, documentation and knowledge transfer are part of the plan, not an afterthought.
What would a better working day look like?
Bring us the process you want to improve. We’ll explore the product, technology and delivery work it needs.