Aspects of project objectives – the way to a full description of the desired project result

What are the different perspectives from which the project objective should be described, so that the goal does not get too much moving during the project?

1. The business processes to be mapped
   Preferably a complete list of the actual (usually customer-driven) variations of the value creation process (order-to-cash, i.e. single sale vs. daily delivery of monthly collective invoices, etc.) as well as the supporting processes within the framework of a BPML (Business Process Master List).
2. The cross section functions
   The cross-cutting functions, which are usually used for specific industries, refer to functionalities that can be found in the handling of most processes, e.g..: Use of batch processing, serialization or storage bin management. The function descriptions of SAP’s former midmarket packages provide a good guide to their identification.
3. The regional scope
   This term refers to all locations with their own postal address in which the SAP system is to be used, namely with a specification of the business processes planned to be used at the respective location – also documented in the BPML.
4. The Systemscope
   This list describes the legacy systems to be replaced, specifying the functions, basic statements on data migration and the replacement/elimination of existing interfaces as part of an actual and target representation of the system landscape.
5. The improvements
   The planned improvements to be achieved with the project are expressed in key figures – per function or GF area affected.
6. Milestone planning
   This planning results from the underlying methodical approach for the entire project – and is defined per workstream.
7. Prioritization of costs – quality – time
   A clear prioritisation and specification for the project must be made within the framework of the so-called magic triangle “Cost – Quality – Time”; at this point, management often adorns itself with giving a clear specification, but this is indispensable so that decisions can be made in a targeted manner.
8. The division of tasks
   Within project planning, all tasks must be expressed in critical work results to be produced – preferably with their description/acceptance criteria, the time milestones and with defined, agreed corrective measures in the event of non-compliance within the framework of a so-called RACI matrix (Responsible-Accountable-Consulted-Informed).

If all this is clearly and comprehensively described, one will both be able to define the required internal resources with their necessary intensity of use and – if this takes place within the framework of a partnering model – to call in a system integrator as an external partner, e.g. on the basis of a fixed price contract.
We are talking here about the starting point of the project. However, it will always have to be permissible to readjust all aspects of the project objectives as long as this happens within the framework of a lived scope change request procedure in which the consequences of the change are pointed out and knowingly accepted.

I plan to make these specific tools and their applications available and explain them in detail in podcasts. If you do not want to or cannot wait for it, write me gladly and we will surely find a faster, individual way for you!