business case

Benefit Management Plan

A contract is an agreement that is binding on both parties. Agreements can come in many forms, including contracts, memorandums of understanding, service level agreements, letters of intent, verbal agreements, emails, or other written agreements.

Government and industry standards; laws and regulations; market conditions; organizational culture and political scope; organizational governance framework; stakeholder expectations and risk thresholds.

The organization's standard policies, processes, and procedures; project governance framework; monitoring and reporting methods; templates; and knowledge base of historical information and lessons learned.

Expert Panel; Delphi Technique

brainstorming; focus groups; interviews

Conflict management; guidance; meeting management

include: Project purpose; measurable project objectives and associated success criteria; high-level and requirements; high-level and project description, boundary definition, and key deliverables; overall project risks, overall milestone schedule; pre-approved financial resources; key stakeholders List of names; project approval requirements; project exit criteria; assigned project managers and their responsibilities and authorities; name and authorities of the sponsor or other person approving the project charter.

Identify high-level strategic and operational assumptions and constraints. Used to document all assumptions and constraints throughout the project life cycle. These contents are continuously refined, supplemented, and modified as the project progresses, and require continuous maintenance.

Subplans and baselines output from other planning processes are inputs to this process

Government or industry standards; laws and regulations; body of project management knowledge for vertical markets and specialized areas; organizational structure, culture, management practices and sustainability; organizational governance framework; infrastructure.

The organization's process system; project management plan template; change control procedures; supervision and reporting methods, risk control procedures and communication requirements; relevant information on similar past projects; and a knowledge base of historical experiences and lessons learned.

Brainstorming; checklists; focus groups; interviews

Conflict management; guidance; meeting management

Use meetings to discuss the project approach, determine how work will be performed to achieve project objectives, and develop project monitoring methods; A project kickoff meeting usually marks the end of the planning phase and the beginning of the execution phase.

Sub-management plan: Scope management plan; requirements management plan; schedule management plan; cost management plan; quality management plan; resource management plan; communication management plan; risk management plan; procurement management plan; stakeholder engagement plan

Benchmark: Scope baseline; Schedule baseline; Cost baseline; other components

Change log; lessons learned register; milestone list; project communication record; project schedule; requirements tracking matrix; risk level book; risk report

The organization’s structure, culture, management practices and sustainability; infrastructure; stakeholder risk thresholds

The organization's process systems; problem and defect management procedures and database; performance measurement database; change control and risk control procedures; project information from past projects

Utilize IT software, etc. to improve information collection efficiency and accuracy

Kick-off meeting, technical meeting, agile or iterative planning meeting, daily stand-up meeting, steering group meeting, problem solving meeting, progress follow-up meeting, retrospective meeting, etc.

Raw observations and measurements

The problem log is created for the first time during this process. Document and follow up on all issues through issue logs throughout the project lifecycle

Change requests include necessary preventive actions, corrective actions, defect remediation, updates

Any changes to the project management plan are raised as change requests and processed through the organization's change control process.

Activity list; Assumption log; Lessons learned register; Requirements document; Risk register; Stakeholder register

Lessons Learned Register; Project Team Dispatch Work Orders; Resource Breakdown Structure; Stakeholder Register

Organizational, stakeholder, and customer culture; geographic distribution of facilities and resources; knowledge experts in the organization; legal and regulatory requirements and constraints

The organization's standard policies, processes and procedures; personnel management systems; the organization's communication requirements; formal knowledge sharing and information sharing procedures

Face-to-face interaction helps build the trusting relationships required for knowledge management

Active listening; guidance; leadership; interpersonal communication; political awareness

All projects generate new knowledge

Derived from work performance data, through comparative analysis of variables, it helps to understand the degree of deviation of the project

Purchase Agreements, Subcontractor Agreements, etc.

Project management information systems; infrastructure; stakeholder expectations and risk thresholds; government or industry standards

The organization's standard policies, processes and procedures; financial control procedures; monitoring and reporting methods; problem management procedures; defect management procedures; organizational knowledge base

Alternatives analysis; cost-benefit analysis; root cause analysis; trend analysis; deviation analysis

Voting (unanimous, majority, majority), authoritarian decision making, multi-criteria decision analysis

to make decisions, take action, or draw attention to

Corrective Actions, Preventive Actions, Defect Remediation

Change management plan; configuration management plan; scope baseline; schedule baseline; cost baseline

Estimate basis; demand tracking matrix; risk report

Resource availability, schedule and cost data, earned value reports, burn charts or burndown charts

Decisions about changes within the project baseline are made by the project manager

Alternatives analysis, cost-benefit analysis

Voting, degree-based decision making, multi-criteria decision making

Conduct change control meetings with the change control board

Assumption log, estimation basis, change log, problem log, lessons learned register, milestone list, project communication record, quality control measurement results, quality report, requirements document, risk register, risk report

Includes approved product specifications, delivery receipts, and work performance documentation, and may include partially completed or in-progress deliverables.

Contains complete supporting records used to manage the procurement process, including statements of work, payment information, contractor work performance information, plans, drawings, and other correspondence.

Document analysis, regression analysis, trend analysis, deviation analysis

Closing report meeting, customer summary meeting, experience and lesson summary meeting, celebration party, etc.

This process updates all project files and marks them as final

Summarize project performance with final report