Value Optimisation · EST. 2011 · APAC
Procurement was going to consume half the project timeline. Vendor engaged in 3 weeks, not 3 months.
The Situation
A government agency engaged ZXM to redesign its procurement and contracting process after a funding window opened mid-financial year. The normal lead time to engage a vendor through legal and procurement was three to six months — which would have consumed the majority of the six-month delivery window before a single line of work had been commissioned.
The agency was not dealing with an unreasonable process — the existing procurement model was designed for stability and risk mitigation in a stable-requirements environment. The problem was structural: the contract framework assumed upfront specification of deliverables, which produced two compounding constraints. First, developing a requirements specification to feed the contract typically consumed two to three months on its own, leaving insufficient time for delivery. Second, any scope change during delivery required a formal contract variation, which reintroduced legal and sign-off overhead at precisely the point where momentum was most critical.
What the diagnostic found
Before any redesign was proposed, ZXM mapped the existing procurement workflow to locate where time was actually being consumed. The primary finding was that the specification overhead — not the legal review itself — was the dominant source of delay. Requirements developed in isolation before contracting were both time-consuming to produce and unreliable by the time delivery began, because scope evolves. The handover structure between project management, finance, and legal compounded this: each boundary required rework to translate artefacts between teams, and sign-off sat outside the working team, introducing wait time at each gate.
What changed
ZXM redesigned the contracting architecture around iterative delivery cadences rather than upfront specification. The contract no longer defined what would be built in detail — it defined how the organisation and vendor would collaborate to agree what to build, Sprint by Sprint. Scrum’s events, artefacts, and roles provided the structural backbone: Sprint Goals replaced the Statement of Work for each delivery cycle, and the Product Backlog — explicitly acknowledged in the contract as an evolving artefact — carried the scope forward without triggering a formal variation each time priorities shifted.
The contracting team itself was restructured. ZXM brought project management, procurement, legal, business leadership, and IT into a single cross-functional team operating under a shared cadence. Sign-off authority moved inside the team, which eliminated the handover delays that had previously accumulated at each boundary. Decisions that had taken weeks of back-and-forth were resolved within the Sprint cycle.
The Definition of Done established contracted quality standards without requiring exhaustive upfront specification — it defined documentation, testing, architectural, and accessibility requirements at a level sufficient to govern delivery without creating specification overhead. Vendors responding to the tender were asked to cost on the basis of comparable outcomes from previous projects, rather than from a detailed requirements document that did not yet exist.
What held
Vendor engagement that had been forecast to take three months was completed in three weeks. That recovered five months of delivery time — time that would otherwise have been lost inside the contracting process itself.
The framework held under delivery conditions. The iterative contracting model produced the transparency and collaboration the agency needed without the overhead the original process assumed was unavoidable. The contract’s reduced specificity — once considered a risk — proved to be a structural feature: it allowed requirements to evolve without triggering delays, because evolution was built into the agreement from the start.
The model was adopted for subsequent engagements. The structural redesign of how the agency contracted for delivery outlasted the project that prompted it.
3 weeks to vendor
Procurement and contracting completed in three weeks — down from a forecast of three months.
Zero variation delays
Scope changes handled inside the Sprint cycle — no contract variation, no sign-off delay, no rework queue.
Adopted across the agency
The contracting model was adopted for subsequent engagements — the structural redesign outlasted the project that prompted it.
Related Case Studies
Let's Work Together
Contact us and learn how adopting an agile framework can advance your organisation
