The primary output of the planning process group is the PM plan
Planning happens simultaneously
Throughout the project life cycle, the planning processes are implemented and planning docs are updated
Chat with our AI personalities
High Level requirements Project stakeholders Project requirements Attributes
Requirements depend on the attributes of a product and the needs of the client. Project requirements are the basis for identifying project scope and for all the project planning and control. The project charter provides high-level requirements. Project stakeholders are the source you must consult to collect detailed requirements.
Defining the Project Scope is one of the key activities that will have a direct impact on the project. Without a firmed up and approved scope, no project manager will be able to plan for a successful project. Time & Cost Planning for the project are directly dependent on the Scope.
If you have two separate staffs that are respectively in charge of planning, and of engineering, staffs is correct. You might also have just one staff, that is in charge of both planning and engineering. So this depends upon context.
A planning engineer would be one who prepares plans for system. For example, Gas Distribution Planning engineer would always study increase in demand or other parameters and work on planning the system upgrades and stuff. A project planner on the other hand would just plan details of a project. For example, If you have a project to upgrade your diesel fueled car to a natural gas fueled car. You would have all the details on which parts need to be changed and everything. A project planner will plan the project and decide that all the engine parts are going to be upgraded in first thirty days then he would have other technicians to change fuel system for next 10 days and finally electic technician to change electric parts in next 5 days. That is project planning.