Eight weeks of working together: what you see – and what we need from you

The written scope is set, the fixed price agreed. What happens in the eight weeks that follow? This post walks through the sprint from your side: what you see in each phase, when we need your time – and what you do not have to do.

One point of contact, in both directions

On our side it is simple: you talk to the architect who designs and builds the system. There is no project manager translating between you and the development. On your side the same principle helps: one person who can answer questions or bring in the right colleagues, and who is allowed to make decisions. Who that is, we settle before we start.

Weeks 1 and 2: questions and decisions

The first two weeks are the phase in which we need your time most. We ask about processes, exceptions and examples, we look at the systems already in place, and we make the decisions that would become expensive later: data model, interfaces, deployment target.

The result of this phase is decisions, not screens. We explain them so that you can judge them – for instance why the ERP remains the leading data source, or what the choice of hosting location means for you. What you do for it: be reachable, answer questions, provide access and examples.

Weeks 3 to 6: interim versions

Now the web application, the Android app and the backend take shape in parallel. What you see in this phase are working interim versions: no slides, no screen mock-ups, but software you can operate – even if not everything in it is finished yet.

Your job is to look at these versions, ideally together with the people who will work with them every day, and to say what is wrong. “That field has a different name here.” “We do this step in the opposite order.” This feedback goes into the next version. Anything outside the agreed scope is noted and offered as a build-out – in writing, before it is built.

Weeks 7 and 8: in your environment

The software is delivered where it was decided in week 1 – in your infrastructure or in a European data centre. It runs with real data, and together we check that it does what the scope says. Then we hand over: code, documentation, access credentials.

Afterwards: trial and decision

After hand-over comes a trial phase of two to four weeks with real users in your company. Only then do you decide how to continue: build-out on a milestone basis, monthly development, or take-over by your own team. What that means in detail is covered in the post on hand-over.

How much time to plan for

The honest answer: it depends on your process, and we tell you before the start. But the pattern is always the same. At the beginning we need you for questions. At every interim version we need you to look and give feedback. In between, we work – you do not have to sit in, and you do not have to supervise anything.

What you do not have to do

• No project management. You do not coordinate developers or maintain ticket lists.
• No requirements document. The written scope is the specification. Everything else we clarify in conversation, using examples.
• No daily meetings. We get in touch when there is something to see or to decide.
• No technical decisions. We make those – and explain what they mean for you.