PMBOK® sixth edition Data Flow diagram by english

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 ·
Performance measurement baseline. · Work Performance Data.
AGREEMENTS. · 5.6： 5.04
Assets[1] Requirements management plan.
· Enterprise
Govermment or industry standards ·
·
Lessons learned register. ·
Change management plan. Control
Legal and regulatory requirements and/or constrints 4.1： 2.01 · Assumption log. · 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.
Organizational cluture and policical climate · Requirements documentation.· Scope baseline. Factors relation
Project o AGREEMENTS. · ·
Organizational governance framework Requirements traceability matrix. Cost baseline.
· Organizational
(structured way to provide control,
· Business case. Charter. o Change log. · Change Requests. process
direction, and o Stakeholder engagement plan. o Communications management plan. · Stakeholder register.
·· Benefits management plan. 6.6： 5.05 Assets
coordication through people,policies, and
Business case. PROJECT CHARTER. o Requirements documentation. o Issue log. · Performance measurement baseline.
process to meet organizatinal strategic and operational goals)
13.1： 2.02 ·
Schedule management plan. Control
·
Stakeholders' expectations and risk thresholds
Benefits management plan. Identify · Schedule baseline. · Performance measurement baseline. toBe updates
?
Organizational standard policies,process, and procedures;
· Scope baseline. Schedule. Assumption log.·
Portfolio,program,and project governance framework
Stakeholders. · Communications management plan. · Schedule data. · Work Performance Information.
·
· Basis of estimates.
Schedule management plan.
· Schedule baseline.
(governance functions and · Project schedule. · Lessons learned register. · pl#： aj：
·
Cost baseline.
process to provide guidance and decision making)
o AGREEMENTS.
· Project calendars.
·· Work Performance Data. Schedule forecasts. · Project schedule.
Monitoring and reporting methods o Risk management plan. o Assumption log. · Requirements management plan. · Assumption log. · Resource calendars. Project funding requirements. · Resource calendars. Process
Template(e.g., project charter template) AGREEMENTS. · Stakeholder register. o Change log. · Communications management plan. · Lessons learned register.
プロジェクト資金要求事項
· Risk register.
Historical information and lessons learned repository PROJECT CHARTER. o Project schedule.
o Issue log. · Risk management plan. · Issue log. · Schedule data.
Resource managemt plan. 7.4： 5.06
(e.g., project records and documents,
13.2 ： 3.24 o 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. · Cost management plan. Costs. · Cost management plan. o retreat
(regulations,product standards,and codes of conduct) Stakeholder · Stakeholder engagement 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. documents
Lessons learned repository with information ablut the preferences,actions, and
· Stakeholder engagement plan. · Lessons learned register. · Risk register.
Geographic distribution of facilities and resources. PROJECT CHARTER. o Quality management plan. · Work Performance Data.
Stakeholder register template and instructions
Organization's culture.
o Development approach. · Scope management plan.
Infrastructure.
· Stakeholder register. · Requirements management plan. 8.3： 5.07 · Document
Stakeholder register from previous projects,
Personnel administration. 5.1： 3.02 · Requirements management plan. · component
involvement of stakeholders
Marketplace conditions. · Quality Management Plan. Control reffer
Policies and procedures Plan Scope Quality. · Quality Management Plan.
Management. o Assumption log. o Approved Change Requests.
Historical information and Lessons learned repositories · Lessons learned register.
o Test and evaluation documents. · Deliverables. · Risk register.
Business case. · Stakeholder register. o Lessons learned register. · Work Performance Data. · #
· Scope management plan. · Requirements documentation. o Lessons learned register. · Verified Deliverables.
Test and evaluation documents.
Policies and procedures AGREEMENTS. o Assumption log. · Quality metrics. · Quality control measurements. Process
· Requirements traceability matrix.
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. Validate
· Scope baseline. · 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. 5.3： 3.04 · Lessons learned register. Requirements traceability matrix.
Lesson learned from previous phases or projects.
PROJECT CHARTER. · Requirements documentation. o Quality reports.
Define · Requirements traceability matrix. · Work Performance Data. · 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. 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. · AGREEMENTS. · 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.
Organization cluture and structure. · Scope management plan. o Development approach. · Communications management plan. Communicatio · Communications management plan.
· Stakeholder engagement plan. · Stakeholder engagement plan.
Team resource availabitily and skills and physical resource availability.
· Resource managemt plan. · Work Performance Data. ns. · Issue log.
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. · Change Requests.
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.
management- andcontrol-related policies, procedures and guidelines.
Templates and forms Monitoring and reporting tools. · Stakeholder register. · Scope baseline. · Risk register. · Work Performance Data. Risks. · Issue log.
*Any component plan.
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.
· · PROCEDUREMENT DOCUMENTATION. Control
Milestone list. ·
Safety policies. Project management information system(PMIS) · Schedule management plan. · Quality reports. ·
Procurement management plan. ·
·
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.
Cost baseline.
· Change Requests.
Historical information for similar projects. · Requirements traceability matrix.
Resource location.
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.
Define · Lessons learned register. · Selected sellers. o Quality reports. · · Change Requests.
Cost forecasts.
· Activity list. · Requirements documentation.
Resource availablity. Activities. · Schedule baseline. · Requirements traceability matrix. · AGREEMENTS. · Work Performance Information. · Issue log.
team resource skils. · Cost baseline. · Activity attributes. 13.4： 5.12 · Lessons learned register.
organization culture. ·
Resource managemt
· plan.
Activity list. · Milestone list. · Communications management plan. Monitor ·· Change Requests.
Risk register.
· Issue log.
Published estimating data. · Activity attributes. · Schedule baseline. o Assumption log. · Risk register. · Stakeholder engagement plan.
Stakeholder · Schedule forecasts.
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.
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.
· Basis of estimates. · *Any component Monitor and
Resources. · Assumption log. ·
·
Cost forecasts.
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. o Assumption log.
· Lessons learned register.
· Activity list. · Milestone list. Project Work.
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
Organization work authorization systems. · Schedule management plan.
· Milestone list. o
o
Assumption log.
Project team assignments.
·
·
Configuration management plan.
Change management plan.
·
·
Change log.
Lessons learned register.
Change Control Boad Control.
· Schedule baseline. ·
Organizational calendars.
Published commercial information from commercial databases.
· Scope baseline.
·
·
Activity list.
Activity attributes.
· Project schedule network diagram. o Resource calendars. ·
·
·
Risk report.
Basis of estimates. ·
Requirements traceability matrix.·
Scope baseline.
Cost baseline.
·
·
Milestone list.
Project communications.
Project schedule.
(CCB)
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.
Estimate ·
Standardized proceses. o AGREEMENTS. · Duration estimates. ·
Risk register.
Risk report. · Change Requests.
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.
Activity · Duration estimates. o Performance measurement baseline. · Basis of estimates. · Approved Change Requests.
Durations. · Basis of estimates. ·
Activity attributes. 4.2： 3.01
· Schedule management plan. · Milestone list. · Lessons learned register. · Assumption log. 4.3： 4.01 · Quality control measurements. ·· Issue log *Any component. · AGREEMENTS.
AGREEMENTS. o Assumption log. Develop Activity list.
· 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. or Phase.
Organizational calture and structure can influence cost management; · *Any component 12.2： 4.09 · Requirements management plan.
Market conditions describe what products, services, and results are available in the regional and global market; · Schedule baseline. · Project calendars. · Quality Management Plan.
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; ·
Financial controls procedures · Duration estimates. ·
Risk management plan.
Procurement management plan. · Requirements traceability matrix. · Scope baseline. · Final Report.
· Resource calendars.
Historical information and lessons learned knowledge bases;
Financial databases; 7.1： 3.11 · Cost management plan. · Lessons learned register. · Configuration management plan.
· · Risk register. · Schedule baseline.
·
· Resource requirements.
Cost baseline.
8.2： 4.03 · Cost baseline.
Existing formal and informal cost estimating and budgeting-related policies, procedures, and guidelines.
Plan Cost
· Stakeholder register.
·
· Risk register. Manage ·
Management. · Quality reports.
Quality. · Change Requests. Companies or
Market conditions. · Resource requirements.. · Project schedule. · Quality Management Plan. · Test and evaluation documents. organizations
· Cost management plan. o Risk register. · Lessons learned register.
Published commercial information.
· Scope baseline. o Quality Management Plan. · Quality control measurements. · Work Performance reports. · Project management plan updates
Exchange rates and inflation. · Lessons learned register. ·
·
Quality metrics.
Cost estimating policies. 7.2： 3.12
Risk report. · Quality reports.
· Quality reports.
o Test and evaluation documents. 10.2： 4.07
Cost estimating templates. · Test and evaluation documents.
Estimate Manage
Historical information and lessons learned repository.
Costs. ·
Cost estimates. Communicatio
· Cost estimates. · Basis of estimates.
Business case. · Basis of estimates. · Change log. · Resource managemt plan. ns. · Final Product,Service,
Benefits management plan. · Cost management plan. · Cost estimates. · Assumption log. · Issue log. · Communications 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
Determine · Risk management plan.
The fulctuation of currencies need to be understood and built into the Determine Budget process. Implement
Budget. · Cost baseline. · Risk register. Risk · Change Requests.
Govemmental agency regulations. PROJECT CHARTER. · Lessons learned register. Responces. Issue log.
Rules,standards, and guidelines specific to the application area. · Requirements documentation. Sellers 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.
· Scope management plan. ： ： baseline) o Risk management plan. o Risk register. Risk register.
Working or operating conditions of the project or its deliverables.
· Stakeholder engagement plan. Risk report.
Cultural perceptions.
Organizational quality management system includeing policies,procedures, and guidelines. · Scope baseline. · Change Requests.
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.
· Quality metrics. · Cost baseline.
Management. · Quality Management Plan. PROCEDUREMENT
· Lessons learned register. 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.
Requirements documentation. · Resource managemt plan. · Risk register. · Project schedule. Resources. · Physical Resource Assignments. · Cost baseline.
· ·
Requirements traceability matrix. · Stakeholder register. ·
Resource calendars.
· Project team assignments. · Project team assignments. ·
Preapproved seller lists. · Stakeholder register. · Lessons learned register. o Project team assignments. ·
Resource requirements. o Project team assignments. Resource managemt plan.
Formal procurement policies,procedures, and guidelines. Stakeholder register.
o Resource calendars. · Resource calendars.
Contract types. · Milestone list. 12.1： 3.23 o Risk register. · Change Requests.
· Scope management plan.
Cost-reimburssable contracts. PROJECT CHARTER. Plan · Bid ducuments. 9.4： 4.05
Time and material contracts(T&M). · Procurement statement of work.
Procurement · · 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.
· Schedule baseline.
Stakeholder risk thresholds. PROJECT CHARTER. ? Project schedule. ·
Lessons learned register. · Project schedule. Resource calendars. · Cost baseline.
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.
Geographic distribution of facilities and resources. · Team charter.
· Team Performance assessments. · Change Requests.
Organizational policies and procedures for social media,ethics, and security.
· Stakeholder register. · Communications management plan. · Requirements traceability matrix. · Bid documents. · Team charter.
· Resource managemt plan. · · Resource managemt plan.
Organizational policies and procedures for issues, risk, change, and data management.
Organizational communication requirements.
· Requirements documentation. 10.1： 3.17 · Stakeholder engagement plan. · Risk register. Make-or-buy decisions. 9.5： 4.06
Standardized guidelines for development, exchange,storage,and retrieval of information. Plan · Independent cost estimates. Manage Team.
Historical information and lessons learned repository. Communications · Issue log.
Stakeholder and commuincations data and information from previous projects. Managrement. · Stakeholder register. ·
· Project schedule. · Lessons learned register. ·
Issue log.
Lessons learned register.
PROJECT · Project team assignments. · Project team assignments.
PROJECT · Team charter.
MANAGEMENT DOCUMENTS.[1] 13.3： 4.10 · Change Requests.
The enterprize environment factors that can influence that can influence
· Quality Management Plan.
the Plan Risk management process
· Lessons learned register. PLAN.[1] Manage
Organizational risk policy.
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. · Risk management plan. PLAN.[2] · Scope management plan. · Stakeholder register.
· Scope baseline. Management. · *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)
· Stakeholder register. · Requirements documentation. · Resource managemt plan. o Lessons learned register. · Resource breakdown structure.
Organizational and project process controls.
· 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. issue and defect resoution , and action results.
Published material, includeing commercial risk database or checklists. 11.3： 3.20 · Lessons learned register. · 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. · Cost baseline. DOCUMENTS.[2] risk registers,risk reports,
DOCUMENTS.[4]
· Scope baseline. 11.4： 3.21 · Risk report. · ： Risk report.
and lessons learned repository).
ORGANIZATIONAL·
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. {Completed checklists} Environmental
11.5： 3.22 · · Risk register. · Organizational
Lessons learned repositories from similar projects.
Plan Risk ·
Schedule baseline.
Cost baseline. · Risk report. process (Configuration Management system) Factors
· Organizational
Responces. Assets[2]
process
(Specific, situation, verification and audit) Assets[3]