Every project is organised into four phases with defined deliverables. The working model and the frequency of follow-up are agreed with each client to suit its organisation.
Each phase ends with a specific deliverable, so the client knows the status of the project and the associated cost at all times.
A study of the company from the inside: how it works, which systems it uses and what it needs to solve. Requirements are gathered with the people responsible for each process.
DeliverableAn analysis of processes and systems, with prioritised requirements.
Definition of the right solution and technology, and a joint choice of the working model that best suits the project.
DeliverableA technical proposal with scope, architecture, working model and budget.
The solution is built according to the agreed model. The client follows progress and approves each delivery before work continues.
DeliverableWorking deliveries, ready to test and approve.
Deployment of the solution, team training and follow-up with support and maintenance.
DeliverableThe solution in production, a trained team and user documentation.
Every project is different. Three questions indicate how yours could be organised.
Answer the questions to see the result.
Depends on the first two questions.
Depends on the third question.
Depends on the working model.
This is guidance, not a commitment: the working model and the frequency of follow-up are agreed in the technical proposal and can be adjusted during the project.
For every relevant decision, we present the alternatives with their advantages and drawbacks, in clear terms. The decision rests with the client, with all the information it needs.
None is better in the abstract. In the technical proposal, the one that best suits the project and its budgeting is chosen together with the client.
Requirements are defined and documented at the start. With scope and timelines fixed, development moves phase by phase through to delivery.
The core of the project (main requirements, architecture and critical integrations) is fixed and documented, and the rest is developed iteratively.
The project starts with a first version covering the essentials and is extended in short cycles. At the end of each cycle, the client has working software and sets the next priorities.
A project works when both sides act as one. This is what we will ask for.
Technical quality does not show in a demo, but it is decisive when software has to grow. These practices are part of every project.