The project order is a document that formally confirms the existence of a project . The project assignment is part of the scope management and is usually signed by a manager at a higher level. The project contract is usually project named and approved the project budget.
The term 'project order' is not standardized and is used differently. Sometimes the term 'order' or 'project agreement' is used in general. The term 'project manager agreement' is often used synonymously, whereby the scope and function of the project mandate go beyond simply naming the project manager. In the case of projects with external service providers, the project assignment is often replaced by a formal contract.
Function in the project management process
The project order is usually preceded by a project application or project proposal in which the initial situation, goals, project results, costs and benefits as well as organization are outlined. Based on the project application, a decision is made about the implementation of a project. The project order is the formal starting signal for the project. This is important because the definition of a project covers a precisely defined period of time. Without a project assignment, the beginning of a project can often no longer be traced back. This then usually leads to problems with billing or accountability.
The term and the content of the project assignment are not standardized. In practice, organizations use different documents that vary considerably in form, scope and content. Since the project order is based on the project application, some of its elements can be found here. The following content can be found in most project assignments:
- Project name
- Start and end of project
- Brief description, company needs and goals
- Project results
- Project budget
- Project manager , possibly project team
- Assumptions and Limitations
- Resource allocation
- DIN ISO 21500 guidelines for project management
- Klose, Burkhard: Project management, 3rd edition 2002, ISBN 3-7064-0520-2