How we work: scope, testing, transition and support
Every project moves in short phases, with success criteria agreed before starting and measured against how your process works today.
The stages of a project
Every software project goes through the same stages. Below we explain in more detail the ones that raise the most questions.
- Discovery: a map of the current process or system.
- Functional document: what the system does and how it is accepted, before building.
- Plan by phases, with a week-by-week schedule and owners.
- Build in versions and validation against the functional document.
- Tests with real data and with key users.
- Formal acceptance.
- Transition with a rollback defined in writing.
- Handover and a bounded follow-up.
Scope in phases
Each project is split into phases, with a week-by-week schedule and a responsibility matrix. The functional document, which describes what the system does and how it is accepted, is closed as a baseline and serves as the delivery criterion. What is in that document is handled as a fix; what is not is quoted as a new feature for a later version.
Baseline: we measure against what already exists
Before the cutover we compare the new system's data against the old system's, record by record, using data snapshots taken on agreed dates. That comparison is our measure that the migration lost and altered nothing. Success criteria are agreed with the client in the functional document, before building.
Testing and acceptance
We test with copies of real production data and compare the full result against the old system. Before that we validate the system against the functional document point by point, and a second person repeats that review independently. Then we run formal tests with key users, case by case, and document acceptance in a report addressed to the client. Tests never alter the client's production environment.
Transition and rollback
During the transition the old system stays active, closed to users, so we can go back to it. Before the cutover we define the rollback plan in writing: what triggers it, who decides and how long it takes.
Handover and follow-up
We deliver functional documentation, user, administration and integration manuals, and an operations runbook for whoever administers the system. Day-to-day operation stays with the client, with training. After launch there is a follow-up period agreed in the project, with a ticket number for every reported incident. Later support is optional and is agreed through a service order.
Frequently asked questions
- How do you know the project worked?
- We compare pilot results against the current process baseline, using the criteria agreed before starting.
- Who owns the code and the data?
- It's defined in writing in each proposal, along with the documentation delivered.
- What if the pilot doesn't deliver the expected result?
- Stop criteria are agreed before starting. If they're met, the project is adjusted or stopped before more is invested.
Request a quote
Tell us which process you want to fix and what you use for it today. We reply within 24 business hours.
Request a quote