How a FIVEX engagement actually runs, week by week, including what happens when the scope moves.
The five steps
We map the system, the constraints and where the risk actually sits.
Nothing is estimated before the unknowns are written down.
We need from you: Access to the people who know the current system, and any documentation that exists.
Flows, interface and the data contracts, before production code.
You approve a clickable prototype rather than a description.
We need from you: One decision-maker who can approve the flows within a week.
Two-week iterations. A demo at the end of each, from the real system.
Scope moves between iterations, never inside one.
We need from you: Attendance at the fortnightly demo, and answers on open questions inside two working days.
Staged rollout with monitoring and alert thresholds agreed in advance.
We rehearse the cutover, including the rollback.
We need from you: A maintenance window, and a named contact on your side for the cutover.
A named engineer with your system in their head.
Fixes, updates and capacity planning, inside an agreed response window.
We need from you: A single channel for requests so nothing arrives only in someone’s inbox.
What a build week looks like
We agree what ships this iteration and what is at risk.
30 minutes, notes in the board.
Working sessions on request. No status meetings.
Questions answered same day.
A running system, not slides.
Recording and a written summary by end of day.
When scope changes
Anyone can raise one, in the board or on the weekly call. It gets written down the same day.
We price the change in days and say what it displaces. No change is absorbed silently.
Either the scope moves out, the date moves, or the change waits. You pick, in writing.
Your organisation on [repository host], with our commits in it from day one.
[board tool], one card per unit of work, visible to you without asking.
One scheduled call, [N] minutes, with the engineers on the work.
Every Friday: what shipped, what did not, what changed.
Send the constraints, the deadline and the hardware. We reply within [N] working days.