133 PMP Mock Exam on Project Scope Management of Chapter 5 in PMBOK 5th Edition

Complete these 133 PMP Mock Exam below that is the best way to learn deeply the concepts included in your materials and prepare well your background for your real examination. With 133 multiple choice questions, it covers the area of project scope management of chapter 5 in PMBOK 5th edition to help you improve effectively your knowledge. Indeed, there are 200 questions that you will face in your real test, and you need to score at least 106 correct answers to pass the exam and obtain Pmp certification. It concludes lots areas of project that not easy to take it if you don’t have enough knowledge. Moreover, to take the Pmp examination, you need to meet the eligibility. If you need more further information of this that you can follow the article Must Read to Know You Meet the Eligibilities to Take a PMP Exam?. At our site, we always update new practice test for you to ensure that you can check your knowledge everyday. Let’s enjoy us to discover this area and memorize all background. Especially, it is 100% free for your practice that you just need to test and hit the submit button to take full automatic answers for your result. Hope it help your practical exam preparation.

Follow the links below to practice more:
256 Practice PMP Exam on Project Time Management from Chapter 6 of PMBOK 5th Edition
185 PMP Mock Exam on Project Cost Management from Chapter 7 of PMBOK 5th Edition
84 Free PMP Performance Domain Questions from Rita’s Course in a Book for Passing the PMP Exam

133 PMP Mock Exam on Project Scope Management of Chapter 5 in PMBOK 5th Edition - Page 1

- Project Scope management process of creating a scope management plan that documents how the project scope will be defined, validated and controlled.- The key benefit of this process is that it provides guidance and direction on how scope will be managed throughout the project.

Process: Plan Scope Mangement
Project Scope Statement
Process: Validate Scope
Process: Collect Requirements

Plurality

Everyone agrees on a single course of action.
1 Inspection2 Group decision making techniques
Describes how the project scope will be managed and controlled.
The largest block in a group decides even if a majority is not achieved.

Requirements Traceability Matrix

Describes how individual requirements meet the business need for the project list all the project, technical, and other types of requirements that must be present for the project product, along with their acceptance criteria.
- The Project Scope Management Process of developing a detailed description of the project and product.- The key benefit of this process is that it describes the project, service, or result boundaries by defining which of the requirements collected will be included in and excluded from the project scope.
The requirements management plan provides the processes that will be used throughout the Collect Requirements process to define and document the stakeholder needs.
A table that links requirements to their origin and traces them throughout the project life cycle.

Process: Collect Requirements

1 Project scope statement2 Project Documents Updates
Input to Plan Scope Management that is used to provide the project context needed to plan the management processes. Provides high-level project description and product characteristics from the SOW.
1 Scope baseline2 Project documents updates
- The Project Scope Management Process of determining, documenting and managing stakeholders needs and requirements to meet the project objectives.- The key benefit of this process is that it provides the basis for defining and managing the project scope including product scope.

1 Expert judgment2 Product analysis3 Alternatives generation4 Facilitated workshops

Tools & Techniques (2) of the Create WBS process
Inputs (4) of the Define Scope process
Tools & Techniques (2) of the Validate Scope process
Tools & Techniques (4) of the Define Scope process

Requirements Management Plan

1 Expert Judgment2 Meetings
1 Scope management plan2 Requirements management plan
Defines the process for managing change on the project.
Describe how requirements will be analyzed, documented and managed.

1 Project management plan2 Requirements documentation3 Requirements traceability matrix4 Work performance data5 Organizational process assets

Inputs (4) of the Define Scope process
Outputs (5) of the Control Scope Process
Inputs (5) of the Validate Scope process
Inputs (5) of the Control Scope Process

An assessment process of multiple alternatives with an expected outcome in the form of future actions resolution.

Group creativity techniques
Group Decision Making Techniques
Project documents updates
Type of Group Decision Making Techniques

Unanimity

1 Variance analysis
1 Expert Judgment2 Meetings
Everyone agrees on a single course of action.
Defines the process for managing change on the project.

Product analysis

Product analysis includes techniques such as product breakdown, systems analysis, requirements analysis, systems engineering, value engineering, and value analysis. (p122)
Project documents that may be updated include, but are not limited to, requirements documentation, which may need to be updated to include approved changes. If approved change requests result from the Create WBS process,then the requirements documentation may need to be updated to include approved changes.
Inspection includes activities such as measuring, examining, and validating to determine whether work and deliverables meet requirements and product acceptance criteria.
1 Project scope statement2 Project Documents Updates

Project Management Plan

1 Plan Scope Management2 Collect Requirements3 Define Scope4 Create WBS5 Validate Scope6 Control Scope
- Unanimity- Majority- Plurality- Dictatorship
- Scope baseline- Scope management plan- Change management plan- Configuration management plan- Requirements management plan
- The scope baseline is the approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be changed only through formal change control procedures and is used as a basis for comparison. - It is a component of the project management plan.

Tools & Techniques (2) of the Validate Scope process

Everyone agrees on a single course of action.
1 Inspection2 Group decision making techniques
Planning and Controlling Process Group
1 Scope baseline2 Project documents updates

Defines the process for managing change on the project.

Requirements Management Plan
Project management plan updates
Scope Management Plan
Change Management Plan

WBS Dictionary

Provides more detailed descriptions of thecomponents in the WBS, including work packages and control accounts (p132)
Describes the work that will be performed and thework that is excluded. It also lists and describes the specific internal or external restrictions or limitations that may affect the execution of the project.
Contains the scope management plan and thescope baseline. The scope management plan specifies how formal acceptance of the completed project deliverables will be obtained. The scope baseline includes the approvedversion of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be changed only through formal change control procedures and is used as a basis for comparison.
Support from more than 50% of the members of the group.

A direct way of viewing individuals in theirenvironment and how they perform their jobs or tasks and carry out processes.

Project Scope
Work Packages
Inspection
Observations

Scope Management Plan

1 Scope management plan2 Requirements management plan
Support from more than 50% of the members of the group.
Describes how the project scope will be managed and controlled.
Planning and Controlling Process Group

A technique used to generate different approaches to execute and perform the work of the project. (p123)

Observations
Alternatives generation
Affinity Diagram
Accepted Deliverables

Plan Scope ManagementCollect RequirementsDefine ScopeCreate WBS

Support from more than 50% of the members of the group.
Planning and Controlling Process Group
One individual makes the decision for the group.
Defines the process for managing change on the project.

Organizational process assets

Defines the process for managing change on the project.
• Policies, procedures, and templates for a project scope statement;• Project files from previous projects; and• Lessons learned from previous phases or projects.
- Process for preparing a detailed project scope statement- Process that enables the creation of the WBS from project scope statement-Process that establishes how the WBS will be maintained and approved-Process that specifies formal acceptance fo completed project deliverables will be obtained- Process to control how requests for changes to the project scope statement will be processed.
- Product scope description- Acceptance criteria- Deliverable- Project exclusion- Constraints- Assumptions

Organizational process assets

Monitoring and Controlling Process Group
• Existing formal and informal scope, control-related policies, procedures, guidelines; • Monitoring and reporting methods and templates to be used.
Describes how the project scope will be managed and controlled.
1 Scope baseline2 Project documents updates

Componenets of the Requirements Management Plan

Requirements should be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders. Well-documented requirements make it easier to detect any deviation in the scope agreed for the project or product.
Detailed requirements documentation is essential for understanding what needs to be produced as the result of the project and what needs to be done to deliver the project and its final products.
- Business requirements- Stakeholder requirements- Solution requirements (Functional and Nonfunctional requirements)- Transition requirements- Project requirements- Quality requirements
How requirements will be planned, tracked and reported- How changes to the product will be intitiated, analyzed, traced, tracked and reported as well as the authorization required to approve these changes-Requirements prioritizzation process-Product metrics that will be used and rationale for using them-Traceability structure to reflect which requirement attributes will be captured on the matrix.

A component of the project management planthat establishes the activities for developing, monitoring, and controlling the project scope.

Scope management plan
Expert judgment
Change requests
Change Management Plan

Stakeholder management plan

1 Scope management plan2 Requirements management plan
1 Scope management plan2 Requirements management plan3 Stakeholder management plan4 Project charter5 Stakeholder register
The stakeholder management plan is used to:- understand stakeholder communication requirements - the level of stakeholder engagement in order to assess- adapt to the level of stakeholder participation in requirements activities.
1 Scope management plan2 Project scope statement3 Requirements documentation4 Enterprise environmental factors5 Organizational process assets

Organizational process assets

1 Scope baseline2 Project documents updates
Defines the process for managing change on the project.
• Policies, procedures, and templates for the WBS;• Project files from previous projects;• Lessons learned from previous projects.
Defines the process and criteria for accepting completed products, services, or results. (p123)

Include the number of change requests received, the number of requests accepted or the number of deliverables completed, etc.

Work performance data
Expert Judgment
Scope baseline
Work Packages

Outputs (5) of the Control Scope Process

1 Work performance information2 Change requests3 Project management plan updates4 Project documents updates5 Organizational process assets updates
1 Accepted deliverables2 Change requests3 Work performance information4 Project documents updates
1 Project scope statement2 Project Documents Updates
1 Scope management plan2 Requirements management plan

Configuration Management Plan

Defines those items that are configurable, those items that require formal change control, and the process for controlling changes to such items.
Defines the process for managing change on the project.
1 Scope management plan2 Requirements management plan
Describes how the project scope will be managed and controlled.

Involve comparison with actual or planned practices, such as processes and operations, to those of comparable organizations to identify best practices, generate ideas for improvement, and provide a basis for measuring performance.

Majority
Benchmarking
Constraints
Brainstorming

To ensure that the project includes all the work required, and only the work required, to complete the project successfully

Scope Management Plan
Project documents updates
Project Management Plan
Project Management Scope Management

Project documents updates

Group activities that can be organized toidentify project and product requirements.
- Business requirements- Stakeholder requirements- Solution requirements (Functional and Nonfunctional requirements)- Transition requirements- Project requirements- Quality requirements
Project documents that may be updated include, but are not limited to, requirements documentation, which may need to be updated to include approved changes. If approved change requests result from the Create WBS process,then the requirements documentation may need to be updated to include approved changes.
To ensure that the project includes all the work required, and only the work required, to complete the project successfully

If the approved change requests have an effect on the project besides the project scope, then the corresponding cost baseline and schedule baselines are revised and reissued to reflect the approved changes.

Project documents updates
Change requests
Other Baseline Updates
Scope Baseline Updates

Different types of Requirements

1 Project management plan2 Requirements documentation3 Requirements traceability matrix4 Work performance data5 Organizational process assets
- Business requirements- Stakeholder requirements- Solution requirements (Functional and Nonfunctional requirements)- Transition requirements- Project requirements- Quality requirements
1 Scope management plan2 Requirements management plan
1 Scope management plan2 Project scope statement3 Requirements documentation4 Enterprise environmental factors5 Organizational process assets

Brainstorming

A technique used to generate and collectmultiple ideas related to project and product requirements.
A technique that utilizes a decision matrix to provide a systematic analytical approach for establishing criteria, such as risk levels, uncertainty, and valuation, to evaluate and rank many ideas.
A technique that enhances brainstorming with a voting process used to rank the most usefulideas for further Brainstorming or for prioritization.
Defines the process for managing change on the project.

Components of requirements documentation

- Business requirements- Stakeholder requirements- Solution requirements (Functional and Nonfunctional requirements)- Transition requirements- Project requirements- Quality requirements
- Business requirements- Stakeholder requirements- Solution requirements- Project requirements- Transition requirements- Requirements assumptions, dependencies, and constraints
1 Plan Scope Management2 Collect Requirements3 Define Scope4 Create WBS5 Validate Scope6 Control Scope
Include business requirements, projectmanagement requirements, delivery requirements.

Work performance information produced includes correlated and contextualized information on how the project scope is performing compared to the scope baseline. It can include the categories of the changes received, the identified scope variances and their causes, how they impact schedule or cost, and the forecast of the future scope performance. This information provides a foundation for making scope decisions.

Requirements documentation
Work performance data
Work performance information
Work Packages

Requirements documentation

Everyone agrees on a single course of action.
Requirements should be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders. Well-documented requirements make it easier to detect any deviation in the scope agreed for the project or product.
Describe how requirements will be analyzed, documented and managed.
Describes how the project scope will be managed and controlled.

Inputs (4) of the Plan Scope Management process

1 Project management plan2 Requirements documentation3 Requirements traceability matrix4 Work performance data5 Organizational process assets
1 Scope management plan2 Requirements management plan
1 Project management plan2 Project charter3 Enterprise environmental Factors4 Organizational process assets
1 Work performance information2 Change requests3 Project management plan updates4 Project documents updates5 Organizational process assets updates

1 Interviews2 Focus groups3 Facilitated workshops4 Group creativity techniques5 Group decision making techniques6 Questionnaires and surveys7 Observations8 Prototypes9 Benchmarking10 Context diagrams11 Document analysis

Outputs (4) of the Validate Scope process
Tools & Techniques (11) of the Collect Requirements Process
Outputs (5) of the Control Scope Process
Tools & Techniques (1) of the Control Scope Process

Change requests

Defines the process for managing change on the project.
1 Requirements documentation2 Requirements traceability matrix
1 Scope baseline2 Project documents updates
Analysis of scope performance can result in a change request to the scope baseline or other components of the project management plan. Change requests can include preventive or corrective actions, defect repairs, or enhancement requests. Change requests are processed for review and disposition according to the Perform Integrated Change Control process.

The features and functions that characterize a product, service, or result.

Product Scope
Project Charter
Brainstorming
Deliverable

A formal or informal approach to discoverinformation from stakeholders by talking to them directly.

Constraints
Interviews
Observations
Inspection

Project exclusions

Monitoring and Controlling Process Group
1 Scope management plan2 Requirements management plan
1 Requirements documentation2 Requirements traceability matrix
Generally identifies what is excluded from the project. (p124)

Detailed requirements documentation is essential for understanding what needs to be produced as the result of the project and what needs to be done to deliver the project and its final products.

Inspection
Requirements documentation
Requirements Management Plan
Requirements must be

Describes how individual requirements meet the business need for the project list all the project, technical, and other types of requirements that must be present for the project product, along with their acceptance criteria.

Project documents updates
Requirements traceability matrix
Requirements Management Plan
Requirements Documentation

Context diagrams

The completed deliverables that have not been formally accepted are documented, along with the reasons for nonacceptance of those deliverables. Those deliverables may require a change request for defect repair.
This documentation will be used to select the requirements that will be included in the project.
The context diagram is an example of a scope model. Context diagrams visually depict the product scope by showing a business system (process, equipment, computer system, etc.), and how people and other systems (actors) interact with it. Context diagrams show inputs to the business system, the actor(s) providing the input, the outputs from the business system, and the actor(s) receiving the output.
- The Project Scope Management Process of monitoring the status of the project and product scope and managing changes to the scope baseline.- The key benefit of this process is that it allows the scope baseline to be maintained throughoutthe project.

133 PMP Mock Exam on Project Scope Management of Chapter 5 in PMBOK 5th Edition