Project leaders create a project plan when they launch a project.
In practice, they will often use the company’s standard document templates or plans from past projects.
Therefore, it is not difficult to create a project plan.
However, there are cases in which a project plan with comprehensive content does not lead to a successful project.
From my practical experience, I believe that one of the reasons for this is the content of the project objectives.
In PMBOK, the project management body of knowledge, the project objectives are written as a business case in the project plan.
The business case also includes other information such as return on investment.
The purpose is to get the project approved by higher-level management.
For this reason, the project objectives are often written from a managerial perspective, and the return on investment is often written in terms of cost savings.
However, I believe that for a successful project, it is important to write the project objectives from the perspective of the project members.
Specifically, this means describing the purpose of what the system is being developed for from the perspective of the on-site users.
For example, if the system is to solve a business problem, who is troubled and how, and how will the system solve the problem?
If these objectives are communicated to the project members, they will be more motivated and the project will proceed more smoothly.