This article needs additional citations for verification .(March 2017) |
A project plan, according to the Project Management Body of Knowledge (PMBOK), is: "...a formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among project stakeholders , and document approved scope, cost, and schedule baselines. A project plan may be sumarized or detailed." [1]
The latest edition of the PMBOK (v6) uses the term project charter to refer to the contract that the project sponsor and project manager use to agree on the initial vision of the project (scope, baseline, resources, objectives, etc.) at a high level. In the PMI methodology described in the PMBOK v5, the project charter and the project management plan are the two most important documents for describing a project during the initiation and planning phases.
PRINCE2 defines a project plan as:
The project manager creates the project management plan following input from the project team and key project stakeholders. The plan should be agreed and approved by at least the project team and its key stakeholders.
Many project management processes are mentioned in PMBOK® Guide, but determining which processes need to be used based on the needs of the project which is called Tailoring is part of developing the project management plan. [2]
The objective of a project plan is to define the approach to be used by the project team to deliver the intended project management scope of the project.
At a minimum, a project plan answers basic questions about the project:
To be a complete project plan according to industry standards such as the PMBOK or PRINCE2, the project plan must also describe the execution, management and control of the project. This information can be provided by referencing other documents that will be produced, such as a procurement plan or construction plan, or it may be detailed in the project plan itself.
The project plan typically covers topics used in the project execution system and includes the following main aspects:
The project plan document may include the following sections:
Earned value management (EVM), earned value project management, or earned value performance management (EVPM) is a project management technique for measuring project performance and progress in an objective manner.
Project management is the process of supervising the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.
A work-breakdown structure (WBS) in project management and systems engineering is a deliverable-oriented breakdown of a project into smaller components. A work breakdown structure is a key project management element that organizes the team's work into manageable sections. The Project Management Body of Knowledge defines the work-breakdown structure as a "hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables."
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. Project planning can be done manually or by the use of project management software.
The Project Management Body of Knowledge (PMBOK) is a set of standard terminology and guidelines for project management. The body of knowledge evolves over time and is presented in A Guide to the Project Management Body of Knowledge, a book whose seventh edition was released in 2021. This document results from work overseen by the Project Management Institute (PMI), which offers the CAPM and PMP certifications.
Project management software are computer programs that help plan, organize, and manage resources.
A project manager is a professional in the field of project management. Project managers have the responsibility of the planning, procurement and execution of a project, in any undertaking that has a defined scope, defined start and a defined finish; regardless of industry. Project managers are first point of contact for any issues or discrepancies arising from within the heads of various departments in an organization before the problem escalates to higher authorities, as project representative.
In project management, a schedule is a listing of a project's milestones, activities, and deliverables. Usually dependencies and resources are defined for each task, then start and finish dates are estimated from the resource allocation, budget, task duration, and scheduled events. A schedule is commonly used in the project planning and project portfolio management parts of project management. Elements on a schedule may be closely related to the work breakdown structure (WBS) terminal elements, the Statement of work, or a Contract Data Requirements List.
In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also referred to as the application development life cycle, is a process for planning, creating, testing, and deploying an information system. The SDLC concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both. There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation.
Within quality management systems (QMS) and information technology (IT) systems, change control is a process—either formal or informal—used to ensure that changes to a product or system are introduced in a controlled and coordinated manner. It reduces the possibility that unnecessary changes will be introduced to a system without forethought, introducing faults into the system or undoing changes made by other users of software. The goals of a change control procedure usually include minimal disruption to services, reduction in back-out activities, and cost-effective utilization of resources involved in implementing change. According to the Project Management Institute, change control is a "process whereby modifications to documents, deliverables, or baselines associated with the project are identified, documented, approved, or rejected."
In project management, scope statements can take many forms depending on the type of project being implemented and the nature of the organization. The scope statement details the project deliverables and describes the major objectives. The objectives should include measurable success criteria for the project.
A project management office is a group or department within a business, government agency, or enterprise that defines and maintains standards for project management within the organization. The PMO strives to standardize and introduce economies of repetition in the execution of projects. The PMO is the source of documentation, guidance, and metrics on the practice of project management and execution.
The project documentation (PID) is one of the most significant artifacts in project management, which provides the foundation for the business project.
Project governance is the management framework within which project decisions are made. Project governance is a critical element of any project, since the accountabilities and responsibilities associated with an organization's business as usual activities are laid down in their organizational governance arrangements; seldom does an equivalent framework exist to govern the development of its capital investments (projects). For instance, the organization chart provides a good indication of who in the organization is responsible for any particular operational activity the organization conducts. But unless an organization has specifically developed a project governance policy, no such chart is likely to exist for project development activity.
Terms of reference (TOR) define the purpose and structures of a project, committee, meeting, negotiation, or any similar collection of people who have agreed to work together to accomplish a shared goal.
In project management, a project charter, project definition, or project statement is a statement of the scope, objectives, and participants in a project. It provides a preliminary delineation of roles and responsibilities, outlines the project's key goals, identifies the main stakeholders, and defines the authority of the project manager. More broadly, this document may be referred to as a "Team Charter" for the purpose of formalizing team roles and task structure at the outset of any team-oriented initiative. Teams that approach a task with a mindful design of team dynamics and task structure are more likely to be successful.
In the United States Department of Defense, the Integrated Master Plan (IMP) and the Integrated Master Schedule (IMS) are important program management tools that provide significant assistance in the planning and scheduling of work efforts in large and complex materiel acquisitions. The IMP is an event-driven plan that documents the significant accomplishments necessary to complete the work and ties each accomplishment to a key program event. The IMP is expanded to a time-based IMS to produce a networked and multi-layered schedule showing all detailed tasks required to accomplish the work effort contained in the IMP. The IMS flows directly from the IMP and supplements it with additional levels of detail——both then form the foundations to implement an Earned Value Management System.
A glossary of terms relating to project management and consulting.
The project management triangle is a model of the constraints of project management. While its origins are unclear, it has been used since at least the 1950s. It contends that:
The following outline is provided as an overview of and topical guide to project management: