Visible progress
You see working software during the build, not only at the end.
A clear sequence from business problem to working software. The stages stay fixed; the decisions inside them are made with you.
Every project starts with understanding, not design. We learn how the business works today, what breaks, who is affected and what a better outcome would look like. This is where we tell you if the problem is worth solving in software at all — and if it is, what solving it properly will require.
Output
A shared understanding of the problem, written down and agreed before scope is proposed.
Working rules
You see working software during the build, not only at the end.
What is agreed is what gets built. Anything else is a change request.
Each part of the project has agreed acceptance criteria.
Code, accounts, infrastructure and documentation belong to the client.