The specification sheet can be created for each ERP projectcan be a real burden. This is also because it plays a crucial role from start to finish. Initially, it functions as an important contractual document, then it becomes a guideline, and at the end of the project, it is the checklist. The people behind the requirements specification are the future users. But how can the „experts“ convey important content in such a way that it is also understandable for the ERP provider is clearly comprehensible?
Specifications as a burden
Generally, in a „Statement of Work“ (SoW), the client specifies the requirements for functions and general services. This should be done as precisely as possible. However, this is often not an easy task for the client, as the processes in an ERP project are rather unfamiliar. The burden of responsibility that arises from the SoW also often leads to confusion or incorrect approaches. Therefore, approaches and methods for creating an SoW are more than welcome.
The mix is what makes it.‘
Good prerequisites are a project team that includes experts in the individual company processes, but also people who have the ERP objective as a whole in mind. The company management should also create enough space for all those involved to fulfil the task. However, endless meetings are also no way to achieve a successful specification, which then often ends up in endless detailed verbiage. This is because it makes no sense for either the provider or the future user in the project.
Telling stories
User stories are a very good way of making the creation of a specification pleasant for the writers and still making the result effective.
User stories are not only simple and quick to write, but they also optimally reflect the user's perspective. By simply describing a work process or an application, it's much easier to understand what the user expects from the system. User stories can be used as a basis for discussing and expanding upon topics in meetings, and finally recording them in the requirements specification. To further simplify the creation of a user story, fixed „story templates“ can be created. These templates then capture the user's function, their tool, and what they want to achieve with it. This allows all user stories to be managed effectively and clearly.
Preparing the ERP future with APIs and microservices
Optimisation of the integrated financial system
The future of SAP Business One from 2020
The SAP Business One strategy
SAP takes over coresystems AG
