Question Clearly sourced

Expert knowledge for digital decisions

How does a requirements analysis proceed?

Short answer

Typically in two to three meetings: observing how work is done today; jointly documenting the process; reviewing special cases. The result is a description from which a reliable effort can be derived. The value lies not in the document, but in the questions that are asked for the first time during the process.

The Process

Meeting 1 – Observation. A person from the specialist department demonstrates how they work today. Not just telling, but showing. During this, steps are noticed that no one would have mentioned because they are taken for granted.

Meeting 2 – Documentation. The process is jointly illustrated: Who does what, with what, in what order, and where does it go. Conflicts between departments become apparent for the first time here.

Meeting 3 – Special Cases. What happens in case of cancellation, partial delivery, complaints, returns, or missing tax numbers? This is where costs arise – and this is where it is determined whether an estimate holds.

What is Delivered at the End

A description of the processes, a list of the affected systems, a framework of quantities, and an effort estimation with a range.

Why This is Not Money Wasted

The result belongs to you. You can also obtain other offers with it – and they will be comparable, as all are based on the same scope. Without this foundation, you are comparing prices for different services.

Key facts

Scope
Usually two to three meetings
Most Important Part
The special cases, not the normal case

Ready for your next project?

Free initial consultation - no sales pressure, just clear answers.

Request consultation