Discovery and scope
We talk about users, the tools you have today and the problems. We agree the goal, the constraints and the priorities. The result is a scope for the first stage and a list of questions still to be answered.
How we work
A good project starts by agreeing what should change in how the company operates. We bring order to the needs, show a direction and split delivery into stages you can judge.
We talk about users, the tools you have today and the problems. We agree the goal, the constraints and the priorities. The result is a scope for the first stage and a list of questions still to be answered.
We map the key user journeys and design the screens. We agree the data model, the integrations and the permissions. A prototype lets us discuss how it behaves before building the full system.
We build features and hand them over for review. We gather feedback, agree changes and update priorities. What new requirements mean for scope, timing and cost is discussed before we build them.
We verify the key processes, permissions and integrations. We prepare the environment, the data migration and the launch plan. We agree how your team will confirm the system is ready to work with.
After launch the system needs care and decisions about what changes next. The scope of support, the responsibilities and the further work are agreed in the way we work together.
Questions
It depends on the processes, the integrations, the data and the quality requirements. Once we know the project we can define the scope of an estimate and the assumptions it rests on.
The schedule follows from the scope, the availability of materials and external dependencies. We plan the first stage so that it delivers something useful.
How rights, access and documentation are handed over is set out in the contract, taking the licences of any components into account.
Describe the users, the current process, the biggest problem and the outcome you want. If you have a deadline, a budget or documentation, bring them along.