ERP Guideline: How requirement specifications work
Bernd Zipper
CEO zipcon consulting GmbH | Chairman Initiative Online Print e.V. | Founder Online Print Symposium | speaker | author | advisor | coach | philanthropist
In early November, we discussed standards for the selection of ERP systems. Now we are following this up with the next step, the requirement specifications.
A new ERP system is not selected randomly: After all, it is the backbone of the company. Thus, a structured set of requirements facilitates the thorough preparation for the decision. And to rearrange the terminology once again, as requirement and technical specifications are often mixed up: In the requirement specification, the client defines the entirety of his requirements. The technical specifications later describe in concrete form how and with what the contractor wants to solve these requirements.
Describing requirements
This sounds simple at first. But in most cases it’ s not. When people describe things, they often assume that their counterparts have the same level of knowledge. Assumptions that are taken for granted are therefore not explained in detail. In addition, in any communication between sender and receiver, information does not arrive or is left to be interpreted by the receiver. All of this can lead to misunderstandings and confusion.
On the other hand, aspects that would be helpful or even indispensable for a correct understanding are often overlooked. Many approach this by giving detailed descriptions of all requirements. However, this has the disadvantage that the volume of work is enormously high, and the requirement specifications turn in to an overflow of work that can no longer be mastered.