Project planning

Project planning is part of project management, which relates to the use of schedules such as Gantt charts to plan and subsequently report progress within the project environment.[1] Project planning can be done manually or by the use of project management software.

Description

Initially, the project scope is defined and the appropriate methods for completing the project are determined. Following this step, the durations for the various tasks necessary to complete the work are listed and grouped into a work breakdown structure. Project planning is often used to organize different areas of a project, including project plans, work loads and the management of teams and individuals. The logical dependencies between tasks are defined using an activity network diagram that enables identification of the critical path. Project planning is inherently uncertain as it must be done before the project is actually started. Therefore, the duration of the tasks is often estimated through a weighted average of optimistic, normal, and pessimistic cases. The critical chain method adds "buffers" in the planning to anticipate potential delays in project execution.[2] Float or slack time in the schedule can be calculated using project management software.[3] Then the necessary resources can be estimated and costs for each activity can be allocated to each resource, giving the total project cost. At this stage, the project schedule may be optimized to achieve the appropriate balance between resource usage and project duration to comply with the project objectives. Once established and agreed, the project schedule becomes what is known as the baseline schedule. Progress will be measured against the baseline schedule throughout the life of the project. Analyzing progress compared to the baseline schedule is known as earned value management.[4]

The inputs of the project planning phase 2 include the project charter and the concept proposal. The outputs of the project planning phase include the project requirements, the project schedule, and the project management plan.[5]

gollark: Yes, not leaking memory is good.
gollark: It can even compile to WASM, hence browser NAP™.
gollark: Yes, rust good?
gollark: The standard library is a TOTAL apiohazard.
gollark: I mean, it is somewhat annoying, yes.

See also

References
  1. Harold Kerzner (2003). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (8th ed.). Wiley. ISBN 0-471-22577-0.
  2. "Definition of project planning methodologies with examples". Retrieved 24 April 2014.
  3. Richard H. Thayer, Edward Yourdon (2000). Software Engineering Project Management (2nd ed.). Wiley-IEEE Computer Society Press. ISBN 0-8186-8000-8.
  4. Fleming, Quentin (2005). Earned Value Project Management (Third ed.). Project Management Institute. ISBN 1-930699-89-1.
  5. Filicetti, John, Project Planning Overview, PM Hut (Last accessed 8 November 2009).
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.