1. Initiating
Stages Project documents Major output
1.1. Develop Project Charter Assumption log (A list of things that Project Charter ( Formally authorizes the existence of the
you perceive to be true (assumptions) project and it assigns the Project Manager and their Authority
and things that might constrain the Level)
project.) * Signed by the organization Senior Management
* High Level requirements & risks
* Preliminary Project Budget and Schedule
* Project Purpose or justification
Assumption Log (A list of things that you perceive to be true
(assumptions) and things that might constrain the project.)
1.2. Identify Stakeholders Stakeholder register (A list of all Stakeholder register (A list of all stakeholders, which can
stakeholders, which can include include categorization, impact, and communication
categorization, impact, and requirements)
communication requirements)
, 2. Planning
Stages Project documents Major output
2.1 Develop Project Management Plan Project Management Plan (Outlines how the project is executed, monitored and
controlled, and closed.)
(4 Baselines: Scope, Schedule, Cost, Performance Measurement Baseline) + 14
Subsidiary plans
Scope Baseline = a detailed outline of the activities, resources, and deliverables
associated with the project.
Project Life Cycle Description
Performance Measurement Baseline = Blend of the schedule and budget information
together. It’s a time-phased view of what needs to be done and how much it costs.
Change Management Plan = Management of changes related to project management
plans, processes, and baselines.
Configuration Management Plan = Management of changes related to project scope.
Scope
2.2 Plan Scope Management Scope Management Plan ( not a physical document, but rather a series of
implementations that help manage project scope. It’s a plan for how the project scope
will be documented, rolled out, and approved by stakeholders.)
Elements:
* Define who the project stakeholders are and what they want out of the project
* Detail the project requirements in a SOW (Scope of Work)
* Further, break down project tasks with a WBS (Work Breakdown Structure).
* Decide and document how the WBS will be controlled and kept up to par.
* Determine how deliverables will be handed to stakeholders.
* Prepare a change control process to effectively handle change requests.)
Requirements Managements Plan
Collection- gathering the basic needs of stakeholders
Categorization – categorizing those needs
Prioritization – prioritizing those needs and identifying “must haves”
Tracing – tracking how those needs are addressed throughout the life of the project
Change Management – the process by which we will change our requirements as needs
change
Verification – how we will verify that requirements have been met
2.3 Collect Requirements Requirements documentation (Description of all
requirements from project stakeholders)
Requirements traceability matrix (A table that traces the
origin of the requirements.)
2.4 Define Scope Project scope statement (A detailed description of the
project or phase deliverables)
2.5 Create WBS Scope Baseline (a detailed outline of the activities, resources, and deliverables
associated with the project). Includes:
* Project Scope Statement (a detailed description of the project or phase deliverables)
* WBS (Breakdown of the project deliverables from the scope statement)
* WBS Dictionary (It should include team member assigned to it, time estimate, cost
estimate, account information, work package ID, quality requirements, contract
information, Scheduled Milestone, plus detail overall of the task at hand)
Time
2.6 Plan Schedule Management Schedule Management Plan (defines how the project schedule is managed
throughout the project lifecycle. The plan provides guidance and sets expectations for
project schedule policies and procedures for planning, developing, managing,
executing, and controlling the project schedule.)
Stages Project documents Major output
1.1. Develop Project Charter Assumption log (A list of things that Project Charter ( Formally authorizes the existence of the
you perceive to be true (assumptions) project and it assigns the Project Manager and their Authority
and things that might constrain the Level)
project.) * Signed by the organization Senior Management
* High Level requirements & risks
* Preliminary Project Budget and Schedule
* Project Purpose or justification
Assumption Log (A list of things that you perceive to be true
(assumptions) and things that might constrain the project.)
1.2. Identify Stakeholders Stakeholder register (A list of all Stakeholder register (A list of all stakeholders, which can
stakeholders, which can include include categorization, impact, and communication
categorization, impact, and requirements)
communication requirements)
, 2. Planning
Stages Project documents Major output
2.1 Develop Project Management Plan Project Management Plan (Outlines how the project is executed, monitored and
controlled, and closed.)
(4 Baselines: Scope, Schedule, Cost, Performance Measurement Baseline) + 14
Subsidiary plans
Scope Baseline = a detailed outline of the activities, resources, and deliverables
associated with the project.
Project Life Cycle Description
Performance Measurement Baseline = Blend of the schedule and budget information
together. It’s a time-phased view of what needs to be done and how much it costs.
Change Management Plan = Management of changes related to project management
plans, processes, and baselines.
Configuration Management Plan = Management of changes related to project scope.
Scope
2.2 Plan Scope Management Scope Management Plan ( not a physical document, but rather a series of
implementations that help manage project scope. It’s a plan for how the project scope
will be documented, rolled out, and approved by stakeholders.)
Elements:
* Define who the project stakeholders are and what they want out of the project
* Detail the project requirements in a SOW (Scope of Work)
* Further, break down project tasks with a WBS (Work Breakdown Structure).
* Decide and document how the WBS will be controlled and kept up to par.
* Determine how deliverables will be handed to stakeholders.
* Prepare a change control process to effectively handle change requests.)
Requirements Managements Plan
Collection- gathering the basic needs of stakeholders
Categorization – categorizing those needs
Prioritization – prioritizing those needs and identifying “must haves”
Tracing – tracking how those needs are addressed throughout the life of the project
Change Management – the process by which we will change our requirements as needs
change
Verification – how we will verify that requirements have been met
2.3 Collect Requirements Requirements documentation (Description of all
requirements from project stakeholders)
Requirements traceability matrix (A table that traces the
origin of the requirements.)
2.4 Define Scope Project scope statement (A detailed description of the
project or phase deliverables)
2.5 Create WBS Scope Baseline (a detailed outline of the activities, resources, and deliverables
associated with the project). Includes:
* Project Scope Statement (a detailed description of the project or phase deliverables)
* WBS (Breakdown of the project deliverables from the scope statement)
* WBS Dictionary (It should include team member assigned to it, time estimate, cost
estimate, account information, work package ID, quality requirements, contract
information, Scheduled Milestone, plus detail overall of the task at hand)
Time
2.6 Plan Schedule Management Schedule Management Plan (defines how the project schedule is managed
throughout the project lifecycle. The plan provides guidance and sets expectations for
project schedule policies and procedures for planning, developing, managing,
executing, and controlling the project schedule.)
