Project purpose

high level requirements

Overall project risk

High-level and project description, boundary definition, main deliverables

Overall milestone schedule

Pre-approved financial resources

List of key stakeholders

Project approval requirements

Project exit criteria

pm and its responsibilities and rights

Sponsor’s name and authority

effect

If the scope changes, choose a cost compensation contract

Unable to provide accurate work instructions, expand staff, hire experts, seek external support and contract labor and materials

Reach a consensus and use guidance

Update organizational process assets

Assumptions

Constraints

exclusions

Scope description

Deliverables

Acceptance Criteria

Further breakdown of deliverables

More detailed than a scope statement

Determine what happened and change it

Uncertain events and taking risks

Quantitative analysis

response

project scope statement

Output of defined activities (activity list, activity attributes, milestone list)

When seeing the product/deliverable description, I often choose SOW

When seeing detailed descriptions of projects and products, they often choose the scope statement

The acceptance criteria are quality requirements. The acceptance criteria look for the quality management plan.

Recurring defects require quality audit

Early testing has a preventive effect

quality cost

Pareto chart to find key and important reasons for decision-making

Sensitivity and confidentiality require changing communication methods

communication technology

Conduct retrospective reviews (regular reviews to record lessons learned) in order to correct and improve the process (if necessary)

Re-prioritize remaining work plan (backlog items)

Determine the current status of project progress by comparing the total amount of work delivered and accepted in the previous time period to the estimate of work completed

DoD is the description of quality requirements in agile.

Stakeholder issues are best dealt with directly by management stakeholders. Learn more.

critical path method

simulation

Resource optimization technology

Confirmed and signed by both the client and the sponsor

Review differences between target performance and actual performance

progress report

status report

Status of all change requests

The former focuses on deliverable acceptance

The latter focuses on deliverable correctness and whether quality requirements are met

Controlling quality (internal validation) usually precedes validating scope (internal/customer validation)

initiate meeting

kick off meeting

get things done

4.1 Develop a project charter

13.1 Identifying interested parties

4.7Technical projects or phases

Summing up experience and lessons, the more people come, the better.