Reference：

• Enterprise ”A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – 4,5,6 Edition”
Environmental BUSINESS Project initiator, Copyright © 2012,2018,jumnichi Kose edited Companies or
Factors DOCUMENTS. Sponsor organizations
• Organizational o AGREEMENTS. • Change Requests.
process •
AGREEMENTS.
Performance measurement baseline.
5.6：5.04
Assets[1] • Requirements management plan.
• Enterprise
•
•
Lessons learned register. •
Change management plan. Control
Assumption log.
Govermment or industry standards
Legal and regulatory requirements and/or constrints 4.1：2.01 • • Requirements documentation.
Scope management plan.
Scope.
• Performance measurement baseline.
• Environmental
• Scope baseline. Scope management plan.
Marketplace conditions
Develop • Requirments traceability matrix. • Work Performance Information. • Lessons learned register. • Schedule baseline.
Factors
Organizational cluture and policical climate
o AGREEMENTS. • Work Performance Data. • Requirements documentation.• Scope baseline. relation
Organizational governance framework Project • •
Requirements traceability matrix. Cost baseline.
• Organizational
Charter.
(structured way to provide control,
direction, and o Stakeholder engagement plan. o Communications management plan. o Change log. • Change Requests. process
coordication through people,policies,•and Business case. o • Stakeholder register. 6.6：5.05 Assets
Business
• strategic case. PROJECT CHARTER.
Requirements documentation. o Issue log. • Performance measurement baseline.
process to meet organizatinal
•
and operational goals)
Benefits management plan. 13.1：2.02 Schedule management plan.
• Control
• Benefits
Stakeholders' expectations and risk thresholds
management plan. Identify • Schedule baseline. • toBe updates
?
Performance measurement baseline.
Organizational standard policies,process, and procedures;
• • • Scope baseline. • Work Performance Data. Schedule. • Assumption log.•
Work Performance Information.
Schedule management plan.
Portfolio,program,and project governance framework
Stakeholders. Communications management plan. Schedule data.
• • Basis of estimates. •
pl#：aj＃
• Project schedule. Schedule baseline.
(governance functions and • Lessons learned register. •
• Schedule forecasts.
Cost baseline.
•
process to provide guidance and decision making)
o AGREEMENTS. o Risk management plan. o Assumption log. • Requirements management plan. •
Project calendars.
•
• Project schedule.
Process
Monitoring and reporting methods
• Stakeholder engagement plan. • Assumption log. Resource calendars. Project funding requirements. • Resource calendars.
Template(e.g., project charter template) AGREEMENTS. • Stakeholder register. o Change log. • Communications management plan. • Lessons learned register.
プロジェクト資金要求事項
• Risk register.
PROJECT CHARTER. o Project schedule.
Issue log. • Risk management plan. • Issue log. • Schedule data.
7.4：5.06
Historical information and lessons learned repository
o
(e.g., project records and documents,
13.2 ：3.24 o Resource managemt plan. o Risk register. • Stakeholder engagement plan. • Risk register. • output
information about the results of previous project selection decision, Control
information about previous project performance.) Plan • Performance measurement baseline. • Performance measurement baseline.
Govermment or industry standards
Stakeholder engagement plan. • Costs. • Cost management plan. o retreat
(regulations,product standards,and codes of conduct) Stakeholder • Cost management plan.
• Cost baseline. • Work Performance Information. • Assumption log. • Cost baseline.
Global,regional, or local trends and practices or habits; • Basis of estimates.
Engagement. • Cost forecasts. • Cost estimates.
organizational culture,political climate, and governance framework
o Project life cycle description. • Lessons learned register.
• Lessons learned register. documents
• Stakeholder engagement plan.
Lessons learned repository with information ablut the preferences,actions, and Risk register.
Organization's culture. PROJECT CHARTER. o Quality management plan. • Work Performance Data.
•
Geographic distribution of facilities and resources.
Stakeholder register template and instructions
Infrastructure.
o Development approach. • Scope management plan.
Stakeholder register from previous projects, • Stakeholder register. • Requirements management plan. 8.3：5.07
Personnel administration. 5.1：3.02 • Requirements management plan. • component
involvement of stakeholders
Marketplace conditions. • Quality Management Plan. Control • Document
Policies and procedures Plan Scope Quality. • Quality Management Plan.
Historical information and Lessons learned repositories Management. o Assumption log. o Approved Change Requests. reffer
o Test and evaluation documents. • Lessons learned register.
• Risk register.
Business case. • Stakeholder register. • o Lessons learned register. o Lessons learned register. • Work Performance Data. • Deliverables. • Test and evaluation documents. #
• Scope management plan. Requirements documentation. • • Verified Deliverables. Quality control measurements.
Policies and procedures AGREEMENTS. • Requirements traceability matrix. o Assumption log. Quality metrics. • Process
Historical information and
PROJECT CHARTER. 5.2：3.03 o Risk register. o Test and evaluation
Lessons learned repositories with
Collect documents. • Work Performance Information.
information from previous projects.
Requirements • Quality control measurements.
. • Requirements management plan. 5.5：5.03
• Scope management plan.
• Scope baseline. Validate • Lessons learned register.
Policies, procedures, and template for a project scope statement o Quality reports. Scope. • Requirements documentation.
Project files previous projects
• Scope management plan. • Lessons learned register. • Work Performance Data. • Requirements traceability matrix.
Lesson learned from previous phases or projects. 5.3：3.04
PROJECT CHARTER. • Requirements documentation. o Quality reports.
Define • Requirements traceability matrix. • Change Requests.
Scope.. • Work Performance Information.
Project Scope statement.
•
9.6：5.08
• Assumption log. • Resource managemt plan.
• Requirements documentation. • Project Scope statement. • Requirements documentation. o Issue log. • AGREEMENTS. Control
Industory-specific WBS standards • Assumption log.
external reference sources for creating WBS process • Requirements traceability matrix. • Requirements traceability matrix. o Lessons learned register. Resources. • Issue log. • Resource managemt plan.
o Pysical resource assignment. • Lessons learned register.
• Schedule baseline.
Policies, procedures, and Template for the WBS • Stakeholder register. • Project schedule. • Pysical resource assignment.• Cost baseline.
Project files previous projects • Resource breakdown structure. • Physical Resource Assignments. • Resource breakdown structure.
Lesson learned from previous projects. 5.4：3.05 • Resource requirements. • Work Performance Data. • Change Requests.
• Assumption log. • Risk register.
10.3：5.09 • Work Performance Information.
Create WBS. • Scope baseline.
• Requirements documentation. • Requirments documentation.
Monitor
PROJECT CHARTER. • Communicatio
Development approach.
Communications management plan.
Organization cluture and structure. • Scope management plan. o •
Stakeholder engagement plan. • Communications management plan.
Team resource availabitily and skills and physical resource availability. • Resource managemt plan. • Work Performance Data. ns. Issue log.
• Stakeholder engagement plan.
Scheduling software.
Guidelines and criteria for tailoring the organization's
6.1：3.06 o Risk register. • Issue log. •
• Lessons learned register.
• Lessons learned register. o Project communications. • Stakeholder register.
set of standard process and procedures to satisfy the specific needs of the project. Plan • Project communications.
Commercial database,such as standard estimating data.
Schedule • Work Performance Information.
Historical information and Lessons lerned respositories. Management. o Quality Management Plan. • Issue log. 11.7：5.10
Existing formal and informal schedule development,
o Project schedule. • Risk report. • Risk management plan. Monitor • Assumption log.
• Change Requests.
management- andcontrol-related policies, procedures and guidelines.
• Stakeholder register. • Scope baseline. • Risk register.
Risks. • Issue log.
*Any component plan.
Templates and forms Monitoring and reporting tools.
PROJECT CHARTER. 9.1：3.15 • Lessons learned register. • Lessons learned register. • Closed Procurement
Organizational culture and structure.
Geographic distribution of facilities and resources. Plan • Work Performance Data. •
•
Risk register.
Risk report.
o Risk report.
Existing resources competencies and availability. Resource •Team charter. • Work Performance Information. PROCEDUREMENT
managemtnt. DOCUMENTATION[1].
Marketplace conditions. Organizational culture and structure. • Scope baseline. • Assumption log. 12.3：5.11
Human resource policies and procedures. Organizational calendars. • Resource managemt plan. • Risk register. • Risk register. •
• Requirements management plan.
Physical resource management policies and procedures. Published commercial information from commercial databases. • Milestone PROCEDUREMENT
list. •
DOCUMENTATION.
Procurement management plan. Control
Safety policies. Project management information system(PMIS) • Schedule management plan. • Quality reports. •
• Risk register. • Procurement management plan.
Security policies. lessons learned repository containg historical information regarding activity lists used by previous similar projects. • •
Change management plan.
Procurements. • Stakeholder register.
Resource requirements.
• Risk management plan.
Templates for the resource management plan. Standardized proceses. 6.2：3.07 •
Assumption log.
Stakeholder register. •
Risk management plan.
Schedule baseline. o Approved Change Requests. •
• Lessons learned register.
• Schedule baseline. • Change Requests.
Historical information for similar projects. Requirements traceability matrix.• Cost baseline.
Resource location.
Template that contain a standard activity list or portion of an activity list from previous projext. Define • Lessons learned register.
• Selected sellers. o Quality reports.
•
•
Existing formal and information activity planning-related policies,procedures, and guidelines,such as the schewduling methodology , that considered in the activity definitions.
Activities. • Schedule baseline. • Activity list. Requirements documentation.
Resource availablity.
• Activity attributes.
• Requirements traceability matrix. • AGREEMENTS. • Work Performance Information.
team resource skils. • Cost baseline. 13.4：5.12
organization culture. Resource managemt
• plan.
• Activity list. • Milestone list. •
Communications management plan. Monitor • Change Requests.
• Issue log. • Change Requests.
Published estimating data. • Activity attributes. • Schedule baseline. o Assumption log. • Risk register. • Stakeholder engagement plan.
Stakeholder
Marketplace conditions. • Scope baseline. • Cost baseline. o Cost estimates. •Resource requirements. • Stakeholder register. • Resource managemt plan.
policies and procedures regarding staffing. 9.2：3.16 o Resource calendars. • Basis of estimates. • Lessons learned register. • Work Performance Data. Engagement. • Work Performance Information.
Policies and procedures relationg to supplies and equipment. Estimate o Risk register. • Resource breakdown structure.
• Project communications.
• Cost forecasts.
Historical information regarding typoe of resources used for similar work on previous projects. o Project communications. 4.5：5.01
Activity • Activity attributes. • Assumption log.
• Issue log.
Resources. • Assumption log.
•
•
Basis of estimates.
Cost forecasts.
• *Any component Monitor and • Lessons learned register.
Portfolio and program plans and project dependencies and relationships • Milestone list. • Resource breakdown structure. • Lessons learned register. • Issue log.
Control
Existing formal and informal acrivity planning-related policies,procedures,and • Resource requirements. • Lessons learned register. • Risk register.
• Activity list. o Assumption log. • Milestone list. Project Work. • Schedule forecasts.
guidelines,such as the scheduling methodology that is considered in developing logical relationships • Lessons learned register. • Quality reports. • Work Performance reports.
Templates that can be used to expedite the preparation of networks for project activities • Schedule management plan. • Activity attributes. • Project schedule network diagram.
• Risk register.
Related activity attributes information in templates can also contain additional description useful in sequencing activites 6.3：3.08 • Risk report. • AGREEMENTS. • Change Requests.
• Activity attributes. • Schedule forecasts. 4.6：5.02
Lessons learned repository containg historical information that can help optimize the sequencing process. Sequence Perform
• Activity list. • Change Requests.
Activities. • Assumption log. Integrated
Goverment or industory standards
Project management information system(PMIS) • Milestone list. • Deliverables. Change
Scheduling tools • Milestone list. o Assumption log. •
Configuration management plan. • Change log. Change Control Boad Control.
•
Organization work authorization systems. • Schedule management plan. o Project team assignments. Change management plan.
• Schedule baseline.
• Lessons learned register.
• •
Organizational calendars. • Activity list. • Project schedule network diagram. o Resource calendars. •
Risk report.
Basis of estimates. • Scope baseline. •
Milestone list.
Project communications. (CCB)
Published commercial information from commercial databases.
• Scope baseline. • Activity attributes. • Requirements traceability matrix.• Cost baseline. • Project schedule.
Project management information system(PMIS)
lessons learned repository containg historical information regarding activity lists used by previous similar projects.
6.4：3.09 • Requirements traceability matrix. o Approved Change Requests.
Standardized proceses. Estimate o AGREEMENTS. • Duration estimates. • Risk register.
• Change Requests.
Template that contain a standard activity list or portion of an activity list from previous projext. • Risk report.
Existing formal and information activity planning-related policies,procedures, and guidelines,such as the schewduling methodology , that considered in the activity definitions. Activity • Duration estimates. o Performance measurement baseline. • Basis of estimates. • Approved Change Requests.
Durations. • Basis of estimates. • Activity attributes. 4.2：3.01 4.3：4.01 Issue log *Any component.
• Schedule management plan. • • Assumption log. • Quality control measurements. •• • AGREEMENTS.
AGREEMENTS. • Milestone list. Lessons learned register.
Assumption log. Develop Activity list.
o • Lessons learned register. Direct and • Test and evaluation documents. • Assumption log. • Accepted Deliverables.
• Activity list. o Project team assignments. Project • Lessons learned register.
Government or industory standards
• Scope baseline. • Activity attributes. Management Manage
Communication channels • Resource requirements. o Resource calendars. • Requirements documentation.
6.5：3.10 Plan. Project Work. • Risk register.
Scheduling methodology containing the policies governing schedule model development and maintenance o Risk register. • Stakeholder register.
Project calendar(s). Develop • Any baseline or component plan. Seller proposales 4.7：6.01
Schedule. • Project schedule. • Scope management plan. Close Project
PROJECT CHARTER. • Schedule management plan. • Schedule data. • • Requirements management plan. or Phase.
Organizational calture and structure can influence cost management;
• Schedule baseline. • Project calendars.
*Any component 12.2：4.09 • Quality Management Plan.
Market conditions describe what products, services, and results are available in the regional and global market;
Currency exchange rates for project costs sourced from more than one country; • Activity attributes. • Scope management plan. Conduct • Communications management plan.
Published commercial information; • Schedule management plan. • Requirements management plan. • Risk management plan.
Project management information system;
o Risk management plan. • Assumption log. • Communications management plan. Procurements. •
•
Lessons learned register.
Requirements documentation. • Procurement management plan.
Producttivity difference in different parts of the world can have a large influence on the cost of products; • Risk management plan.
Financial controls procedures • Duration estimates. • Procurement management plan. • Requirements traceability matrix. • Scope baseline. • Final Report.
• Resource calendars.
Historical information and lessons learned knowledge bases;
7.1：3.11 • Cost management plan. • Lessons learned register. • Configuration management plan.
• Risk register.
• Schedule baseline.
•
Financial databases; • Cost baseline.
8.2：4.03 • Cost baseline.
Existing formal and informal cost estimating and budgeting-related policies, procedures, and guidelines.
Plan Cost • Resource requirements. • Stakeholder register.
•
• Risk register. Manage •
Management. • Quality reports.
Quality. • Change Requests. Companies or
Market conditions. • Resource requirements.. • Project schedule. • • Test and evaluation documents. organizations
Published commercial information. • Cost management plan. o Risk register. Quality Management Plan.
• Lessons learned register.
Exchange rates and inflation. • Scope baseline. o Quality Management Plan. • Quality control measurements. • Work Performance reports.
Cost estimating policies.
• Lessons learned register. •
•
Quality metrics.
7.2：3.12 •
Risk report.
Quality reports.
o Test and evaluation documents.
• Quality reports.
10.2：4.07 • Project management plan updates
Cost estimating templates. •
Historical information and lessons learned repository. Estimate Test and evaluation documents.
Manage
Costs. Cost estimates.
• Communicatio
• Cost estimates. • Basis of estimates.
Business case. • • Basis of estimates. • Assumption log.
• Change log. • Resource managemt plan. ns. • Final Product,Service,
Cost management plan. • Cost estimates. • Issue log. • Communications management plan.
Benefits management plan. • Basis of estimates. o AGREEMENTS. • Lessons learned register. • Lessons learned register. • Stakeholder engagement plan. or Result Transition.
AGREEMENTS.
Reporting methods. • Project schedule. • Risk register. • Project funding requirements. •
•
Quality reports.
Risk report.
• Project communications.
Cost budgeting tool • Scope baseline. • Resource managemt plan. o Risk register. • Stakeholder register.
Exsiting formal and informal cost budgeting-related policies,procedures,and guidelines • Risk report.
Historical information and lessons learned repository.
7.3：3.13 11.6：4.08 • Change Requests.
The fulctuation of currencies need to be understood and built into the Determine Budget process. Determine • Risk management plan.
Implement
Budget. • Cost baseline. • Risk register. Risk
Govemmental agency regulations.
Rules,standards, and guidelines specific to the application area.
PROJECT CHARTER. • Requirements documentation. Sellers • Lessons learned register. Responces. Issue log. Customer
geographic distribution. ？ (Requirements of • Risk register. Lessons learned register.
Organizational structure. • Stakeholder register. • Requirements traceability matrix. Cost performance o Assumption log. • Risk report. o Project team assignments. Project team assignments.
Marketplace conditions.
Working or operating conditions of the project or its deliverables. • Scope management plan. 　　baseline) o Risk management plan. o Risk register. Risk register.
Cultural perceptions. • Stakeholder engagement plan. Risk report.
• Scope baseline. • Change Requests.
Organizational quality management system includeing policies,procedures, and guidelines.
Quality template sutch as check sheets, traceability matrix, and others.
8.1：3.14 • Procurement management plan.
Histlical databases and lessons learned repository. Plan Quality • Resource managemt plan.
Management. • Quality metrics. • Cost baseline.
• Quality Management Plan. • Lessons learned register.
PROCEDUREMENT 9.3：4.04
Business case. • Scope baseline. • Risk management plan. DOCUMENTATION[1].
• Requirements traceability matrix. Acquire • Resource managemt plan.
Benefits management plan. • • Resource requirements.. • Quality Management Plan. • Scope baseline. Risk register.
Requirements documentation. • Resource managemt plan. • • Project schedule. Resources. • Physical Resource Assignments. • Cost baseline.
•
Preapproved seller lists. • Requirements traceability matrix. • Stakeholder register. •
Resource calendars.
• Project team assignments. • Project team assignments.
Formal procurement policies,procedures, and guidelines. • Stakeholder register. • Lessons learned register. o Project team assignments.
Resource requirements. o Project team assignments.
• Stakeholder register.
o Resource calendars. • Resource calendars.
Contract types.
• Milestone list. 12.1：3.23 o Risk register. • Change Requests.
Cost-reimburssable contracts. • Scope management plan.
PROJECT CHARTER. Plan • Bid ducuments. 9.4：4.05
Time and material contracts(T&M). •
Procurement Procurement statement of work.
• Resource managemt plan. Develop
• Independent cost estimates. Lessons learned register. • Resource managemt plan.
Organizational cluture,political climate, nad govermanance framework. management. Source selection criteria.
•
• Source selection criteria. Team. Project schedule.
Personnel administration policies. • Procurement management plan. • Lessons learned register. Project team assignments.
Stakeholder risk thresholds. PROJECT CHARTER. ? Project schedule. Lessons learned register.
• • Project schedule. Resource calendars.
Established communication channels,tools, and systems. (Requirements for communication • Milestone list. • Procurement strategy. • Project team assignments. • •
Project team assignments. Work Performance reports. Team charter.
Global,regional, or local trends,practices, or habits. • Stakeholder engagement plan. accompanying progress) • Requirements documentation. • Procurement statement of work. • Resource calendars. • Team Performance assessments. • Change Requests.
Geographic distribution of facilities and resources. • Team charter.
Organizational policies and procedures for social media,ethics, and security. • Communications management plan. • Requirements traceability matrix. • Bid documents. • Team charter.
• Resource managemt plan.
• Stakeholder register. • Resource managemt plan. 10.1：3.17 • Make-or-buy decisions. • Resource managemt plan. 9.5：4.06
Organizational policies and procedures for issues, risk, change, and data management.
Organizational communication requirements.
• Requirements documentation. • Stakeholder engagement plan. • Risk register. • Schedule baseline.
Standardized guidelines for development, exchange,storage,and retrieval of information. Plan • Independent cost estimates. Manage Team. • Cost baseline.
Historical information and lessons learned repository. Communications •
Stakeholder and commuincations data and information from previous projects. Managrement. • Stakeholder register. Issue log.
• Issue log.
• Project schedule. • Lessons learned register. • Lessons learned register.
PROJECT • Project team assignments. • Project team assignments.
PROJECT • Team charter.
The enterprize environment factors that can influence that can influence MANAGEMENT DOCUMENTS.[1] 13.3：4.10 • Change Requests.
• Quality Management Plan.
the Plan Risk management process
Organizational risk policy. • Lessons learned register. PLAN.[1] Manage
Risk categories, possibly organized into a risk breakdown structure. Stakeholder • Communications management plan.
Common defintion of risk concepts and team.
• Stakeholder register. • Communications management plan. • Change log. Engagement.. • Stakeholder engagement plan.
Risk statement formats.
Template for the risk managemant plan, risk register, and risk report. • Any baseline or component plan. • Risk management plan. • Issue log.
• Stakeholder engagement plan.
Roles and responsibilities.
• Change management plan. • Lessons learned register.
Authority levels for decision making. PROJECT CHARTER. PROJECT (Issue log) • Stakeholder register.
Lessons learned repository from previous similar projects.
11.1：3.18 • Change log.
MANAGEMENT • Issue log.
Plan Risk • Deliverables. • Lessons learned register.
Business case. • PLAN.[2] • Scope management plan. • Stakeholder register.
• Scope baseline. Management. Risk management plan.
• *Any component 4.4：4.02
AGREEMENTS. (WBS dictionary • Resource requirements.. Manage
Published material, includeing commercial risk database or checklists. • Requirements management plan. (technical documents, • Risk management plan. Project • Project management plan updates
Academic studies. (quality requirements, etc.)) " • Cost management plan. Knowage.
benchmarking results. • Schedule baseline. PROCEDUREMENT DOCUMENTATION.
*Any component
• Lessons learned register.
(Change based on the official procedure
Industry stdsies of similar projects. • Schedule management plan. • Cost baseline. • Duration estimates. Modified version of all auxiliary
Project files, including actual data. • Basis of estimates. • Project team assignments. management plan)
Organizational and project process controls. • Stakeholder register. • Requirements documentation. • Resource managemt plan. o Lessons learned register. • Resource breakdown structure.
• Lessons learned register. 11.2：3.19 o Project team assignments.
Risk statement formats.
PROJECT • Source selection criteria. PROJECT
Checklists from previous similar projects.
Identify Risks. o Resource calendars. • Organizational standard policies,process, and procedures. • Stakeholder register.
• Risk register. MANAGEMENT • Issue and defect management procedures defining MANAGEMENT
• Risk report. PLAN.[3] issue and defect control,
• Lessons learned register. PLAN.[4]
• Stakeholder register. • Risk register. • Assumption log. •
issue and defect identification and resolution ,and action item tracking.
Issue and defect management database(s)
Industory studies of similar projects. • Assumption log. • Issue log. containing historical issue and defect status,
• Risk management plan.
Published material, includeing commercial risk database or checklists. 11.3：3.20 • Lessons learned register. •
issue and defect resoution , and action results.
Performance measurement database used to collect
The organizational process assets that can influence Perform Qualitative Risk Analysis include. Perform and make available measurement data on process and products.
Qualitative • Lessons learned register. • Change control and risk control procedures.
• Risk register. • Project schedule. • Project information from previous projects.
Risk Analysis. • Risk report. • Requirements documentation.
(e.g. scope,cost,schedule,
performance measurement baseline,
• Risk management plan. • Risk register. • Assumption log.
PROJECT • Risk register. project calendars,
• Schedule baseline. • Issue log. • Stakeholder register. project schedule network diagrams, PROJECT
Industory studies of similar projects. DOCUMENTS.[2] risk registers,risk reports,
DOCUMENTS.[4]
• Cost baseline. and lessons learned repository).
ORGANIZATIONAL
•
• Scope baseline. 11.4：3.21 • Risk report. • ＋Risk report.
Published material, includeing commercial risk database or checklists.
The organizational process assets that can influence Perform Qualitative Risk Analysis include. • Lessons learned register. Perform Project Management PROCESS ASSETS.
updates
Quantitative • Schedule management plan. • Information on qualified sellers.

• Cost baseline. • Project schedule.

Risk Analysis. •
•
Cost management plan.
Quality Management Plan.
•
•
Assumption log.
Cost forecasts.
Information System (Management of defect and issues)
（Causes of variances,
The risk appetite and threshold of key stakeholders • Resource managemt plan. • Lessons learned register. Corrective action chosen
Templates for the risk management plan, risk register, and risk report.
• Risk management plan.• Risk register.
• Procurement management plan. •
•
Project schedule.
Project team assignments.
(PMIS) and the reasons,lessons learned） • Enterprise
Historical databases. • Resource managemt plan. • Scope baseline. Environmental
11.5：3.22 • Schedule baseline. • Risk register. • Organizational {Completed checklists}
Lessons learned repositories from similar projects.
Plan Risk • Cost baseline. • Risk report. process (Configuration Management system) Factors
• Organizational
Responces. Assets[2]
process
(Specific, situation, verification and audit) Assets[3]
 • Enterprise
Environmental BUSINESS Project initiator,
Factors DOCUMENTS. Sponsor
• Organizational
process
Assets[1] AGREEMENTS.
Govermment or industry standards 4.1：2.01 o Requirements documentation.
Legal and regulatory requirements and/or constrints
Marketplace conditions Develop
Organizational cluture and policical climate
Organizational governance framework Project
(structured way to provide control,
Charter.
Stakeholder engagement plan.
direction, and
o o Communications management plan.
Stakeholder engagement plan.
coordication through people,policies, and
• Business case.
process to meet organizatinal strategic and operational goals) o o Communications management plan.
•
Stakeholders' expectations and risk thresholds Business case. PROJECT CHARTER. 13.1：2.02 o Requirements documentation.
•
Organizational standard policies,process, and procedures; Benefits management plan. 13.1：2.02
•
Portfolio,program,and project governance framework Benefits management plan. Identify
(governance functions and ? • Communications management plan. Identify
process to provide guidance and decision making)
Stakeholders. • Communications management plan.
Monitoring and reporting methods
Template(e.g., project charter template) Stakeholders.
Historical information and lessons learned repository • Requirements management plan.
(e.g., project records and documents,
information about the results of previous project selection decision, AGREEMENTS. • Stakeholder register. • Stakeholder engagement plan. • Communications management plan. • Requirements management plan.
information about previous project performance.) PROJECT CHARTER. o Project schedule.
• Risk management plan. • Stakeholder register. • Communications management plan.
Resource managemt plan. o Project schedule.
13.2 ：3.24 o • Stakeholder engagement plan. • Risk management plan.
13.2 ：3.24 o Resource managemt plan. • Stakeholder engagement plan.
Plan
? Plan
Stakeholder • Stakeholder engagement plan.
Stakeholder • Stakeholder engagement plan. • Stakeholder engagement plan.
Engagement.
Organization's culture. Engagement.
Infrastructure. • Stakeholder engagement plan. o Quality management plan.
PROJECT CHARTER. • Stakeholder engagement plan. o Quality management plan.
Personnel admiknistration.
• • Scope management plan.
Marketplace conditions. • Stakeholder register. Requirements management plan.
• Requirements management plan. • • Scope management plan.
5.1：3.02 • Stakeholder register. Requirements management plan.
• Requirements management plan.
Previous similar projects 5.1：3.02
Information in the industory,discipline, and application data. Plan Scope
Plan Scope
Management.
Management.
Business case.
AGREEMENTS. • Stakeholder register. • Scope management plan. • Requirements documentation. o Lessons learned register.
• Stakeholder register. • Scope management plan. • Requirements documentation. o Lessons learned register.
• Requirements traceability matrix.
PROJECT CHARTER. 5.2：3.03 • Requirements traceability matrix.
5.2：3.03
?Lessons learned register. Collect
o Collect
Requirements
Requirements
.
.

• Scope management plan. 5.3：3.04

PROJECT CHARTER. • Scope management plan. 5.3：3.04
Define
? Define
Scope..
Scope..
• Requirements documentation. • Project Scope statement.
• Requirements documentation. • Project Scope statement.
• Requirements traceability matrix.
• Requirements traceability matrix.

? 5.4：3.05
5.4：3.05
Create WBS. • Scope baseline.
• Requirements documentation. Create WBS. • Scope baseline.
Organization cluture and structure.Team resource availabitily
• Requirements documentation.
and skills
PROJECT CHARTER.
Development approach.
and physical resource availability.Scheduling software.Guidelines and criteria
• Scope management plan. o
Development approach.
for tailoring the organization's
set of standard process
and procedures to satisfy
• Scope management plan. o
the specific needs of the project.Commercial database,such as standard estimating data.Historical information and 6.1：3.06
Lessons lerned respositories.Existing formal and informal schedule development, 6.1：3.06
management- andcontrol-related policies, procedures and Plan
guidelines.Templates and formsMonitoring and reporting tools. Plan
Schedule
Schedule
Management. o Quality Management Plan.
o Project schedule. Management. o Quality Management Plan.
PROJECT CHARTER. • Stakeholder register. • Scope baseline. o Project schedule.
Organizational culture and structure. 9.1：3.15 • Stakeholder register. • Scope baseline.
Geographic distribution of facilities and resources. 9.1：3.15
Plan
Existing resources competencies and availability.
Plan
Marketplace conditions. Resource
Resource
Human resource policies and procedures. managemtnt.
• Scope baseline. • managemtnt.
Physical resource management policies and procedures.
Safety policies.
Resource managemt plan. • Scope baseline. • Resource managemt plan.
Security policies. • Schedule management plan.
Templates for the resource management plan. • Schedule management plan.
? projects.
Historical information for similar 6.2：3.07
6.2：3.07
Define
Resource location. Define
Resource availablity. Activities. • Schedule baseline. Activities. • Schedule baseline.
team resource skils. • Cost baseline.
organization culture. Resource managemt
• • plan.
Activity list. • Cost baseline.
Published estimating data. • Schedule baseline. Resource managemt
• • plan.
Activity list.
• Activity attributes. • Schedule baseline.
Marketplace conditions. • Scope baseline. • Cost baseline. • Activity attributes.
policies and procedures regarding staffing. 9.2：3.16 • Scope baseline. • Cost baseline.
9.2：3.16
Policies and procedures relationg to supplies and equipment. Estimate
Historical information regarding typoe of resources used for similar work on previous projects. Estimate
Activity
Activity
Resources.
• Milestone list. • Resource breakdown structure. Resources.
• Resource requirements. • Milestone list. • Resource breakdown structure.
• Activity list. • Lessons learned register. • Resource requirements.
• Activity attributes. • Activity list. • Lessons learned register.
• Schedule management plan. 6.3：3.08 • Activity attributes.
• Schedule management plan. 6.3：3.08
? Sequence
Sequence
Activities.
Activities.
Organizational culture and structure.
• Milestone list.
Organizational calendars.
Published commercial information from commercial databases. • Schedule management plan. • Milestone list.
Project management information system(PMIS)
• Activity list. • Project schedule network diagram. • Schedule management plan.
lessons learned repository containg historical information regarding activity lists used by previous similar projects.
• Activity attributes. • Activity list. • Project schedule network diagram.
Standardized proceses.
• Scope baseline. 6.4：3.09 • Activity attributes.
Template that contain a standard activity list or portion of an activity list from previous projext.
Existing formal and information activity planning-related policies,procedures, and guidelines,such as the schewduling methodology , that considered in the activity definitions.
• Scope baseline. 6.4：3.09
Estimate
Estimate
Activity • Duration estimates. o Performance measurement baseline. Activity • Duration estimates.
Durations. • Basis of estimates. o Performance measurement baseline.
• Schedule management plan. • Milestone list. • Lessons learned register. Durations. • Basis of estimates.
• Schedule management plan. • Milestone list. • Lessons learned register.
• Activity list.
AGREEMENTS. • Scope baseline. • Activity attributes. • Activity list.
• Resource requirements. • Scope baseline. • Activity attributes.
6.5：3.10 • Resource requirements.
? 6.5：3.10
Develop
Develop
Schedule.
PROJECT CHARTER. • Schedule management plan. Schedule.
Organizational calture and structure can influence cost management;
Market conditions describe what products, services, and results are available in the regional and global market; • Schedule baseline. • Schedule management plan.
Currency exchange rates for project costs sourced from more than one country; • Schedule baseline.
Published commercial information; • Schedule management plan.
Project management information system; • Schedule management plan.
Producttivity difference in different parts of the world can have a large influence on the cost of products;
Financial controls procedures
Historical information and lessons learned knowledge bases;
Financial databases; 7.1：3.11 • Cost management plan.
Existing formal and informal cost estimating and budgeting-related policies, procedures, and guidelines. 7.1：3.11 • Cost management plan.
Plan Cost
Plan Cost
Management.
Management.
• Resource requirements.. • Project schedule.
• Cost management plan. • Resource requirements.. • Project schedule.
• Scope baseline. o Quality Management Plan. • Cost management plan.
• Lessons learned register. • Scope baseline. o Quality Management Plan.
7.2：3.12 • Lessons learned register.
? 7.2：3.12
Estimate
Estimate
Costs.
Costs.
• Cost management plan. • Cost estimates.
Business case.Benefits • Basis of estimates. • Cost management plan. • Cost estimates.
management plan. • Basis of estimates.
AGREEMENTS. • Project schedule.
• Scope baseline. • Resource managemt plan. • Project schedule.
• Scope baseline. • Resource managemt plan.
7.3：3.13
? 7.3：3.13
Determine
Determine
Budget. • Cost baseline. Budget. • Cost baseline.
PROJECT CHARTER.
• Requirements documentation.
？ (Requirements of • Requirements documentation.
Govemmental agency regulations.
• Stakeholder register. • Requirements traceability matrix. Cost performance ？ (Requirements of
Stakeholder register.
Rules,standards, and guidelines specific to the application area.
geographic distribution. • • Requirements traceability matrix. Cost performance
Organizational structure. • Scope management plan. 　　baseline)
Marketplace conditions. • Stakeholder engagement plan. • Scope management plan. 　　baseline)
Working or operating conditions of the project or its deliverables.
Cultural perceptions. • Scope baseline. • Stakeholder engagement plan.
Organizational quality management system includeing policies,procedures, and guidelines. 8.1：3.14 • Scope baseline.
Quality template sutch as check sheets, traceability matrix, and others. 8.1：3.14
Histlical databases and lessons learned repository. Plan Quality
Plan Quality
Management. • Quality Management Plan.
• Scope baseline. Management. • Quality Management Plan.
Business case. • Risk management plan. • Scope baseline.
Benefits management plan. • Requirements documentation. • Resource requirements.. • • Scope baseline. • Risk management plan.
• Resource managemt plan. Quality Management Plan.
• Requirements documentation. • Resource requirements.. • • Scope baseline.
• Requirements traceability matrix. • Resource managemt plan. Quality Management Plan.
Preapproved seller lists. • Stakeholder register. • Lessons learned register. • Requirements traceability matrix.
Formal procurement policies,procedures, and guidelines. • Stakeholder register. • Lessons learned register.
Contract types. • Milestone list. 12.1：3.23
PROJECT CHARTER. • Scope management plan. • Milestone list. 12.1：3.23
Cost-reimburssable contracts. Plan • Scope management plan.
Time and material contracts(T&M). Plan
Procurement
Procurement
Organizational cluture,political climate, nad govermanance framework. management.
Personnel administration policies. PROJECT CHARTER. • Procurement management plan. management.
Stakeholder risk thresholds. ? Project schedule. • Procurement management plan.
? Project schedule.
Established communication channels,tools, and systems.
• Stakeholder engagement plan. (Requirements for communication
Global,regional, or local trends,practices, or habits. accompanying progress) • Stakeholder engagement plan. (Requirements for communication
Geographic distribution of facilities and resources.
• Stakeholder register. • Communications management plan. accompanying progress)
Organizational policies and procedures for social media,ethics, and security. • Resource managemt plan. • Stakeholder engagement plan. • Stakeholder register.
Organizational policies and procedures for issues, risk, change, and data management.
• Requirements documentation. 10.1：3.17 • Resource managemt plan. • Communications management plan.
Organizational communication requirements.
Plan • Requirements documentation. 10.1：3.17
Standardized guidelines for development, exchange,storage,and retrieval of information.
Plan • Stakeholder engagement plan.
Historical information and lessons learned repository. Communications
Stakeholder and commuincations data and information from previous projects. Managrement. Communications
Managrement.
PROJECT
PROJECT
MANAGEMENT
MANAGEMENT
PLAN.[1]
PLAN.[1]

Risk Review.