Question Clearly sourced

Expert knowledge for digital decisions

How does a requirements analysis proceed?

Short answer

Usually in two to three sessions: observing how work is done today; jointly recording the process; going through special cases. The result is a description from which a reliable workload can be derived. The value lies not in the document, but in the questions that are asked for the first time.

The Process

Session 1 – Observing. A person from the department shows how they work today. Not explaining, but demonstrating. During this, steps are noticed that no one would have mentioned, because they are self-evident.

Session 2 – Drawing. The process is jointly mapped out: who does what, with what, in what order, what goes where. Contradictions between departments become visible for the first time here.

Session 3 – Special Cases. What happens in cases of cancellation, partial delivery, complaint, return, missing tax number? Here, the costs arise – and here it is decided whether an estimate is valid.

What the Final Result Contains

A description of the processes, a list of affected systems, a quantitative framework and a workload estimate with a range.

Why This Is Not a Waste of Money

The result belongs to you. You can use it to obtain other offers – and comparable ones, because all are based on the same scope. Without this foundation, you would be comparing prices for different services.

Key facts

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

Sources

All external claims are backed by traceable sources.
  1. 01

Ready for your next project?

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

Request consultation