1. Completion of a product scope is measured against:
Product Management Plan
Project Management Plan
WBS & WBS Dictionary
Product Requirements
2. All of the below are inputs to Define Scope process EXCEPT:
Project Charter
Requirements Document
Organizational process assets
Project Management Plan
3. Validated deliverables is an input to which of the following processes?
Collect Requirements
Define Scope
Create WBS
Validate Scope
4. Project Charter is an input to all of the following processes EXCEPT:
Collect requirements
Define Scope
Create WBS
Develop Project Management Plan
5. Work Performance Measurement is an output of which process:
Define Scope
Create WBS
Validate Scope
Control Scope
6. If the project is terminated early, the level and extent of completion should be documented. This is done as a part of:
Define Scope
Create WBS
Validate Scope
Control Scope
7. Validate Scope can be BEST described as the process of
Validating that the project quality requirements have been met
Obtaining stakeholder's formal acceptance of the project deliverables
Controlling changes to the scope of the project
Validating that all of the project's objectives have been met
8. Which of the following can be BEST described as a characteristic of Work Package?
May or may not be cost estimated
Can be scheduled
Can be further decomposed into work packages
May be monitored subject to nature of the project
Answers
1. C.
2. D.
3. D. Validated Deliverables are output of Perform Quality Control process and acts as inputs to Validate Scope process.
4. C. Project Charter is input to all these processes except Create WBS.
5. D. Work performance measurement is an output of Control Scope
6. C
7. B. Validate Scope is the process of obtaining the stakeholders' formal acceptance of the completed project scope and associated deliverables. [PMBOK Pg. 123]
8. B. Work Package is the lowest level in the WBS, and is the point, at which it can be reliably scheduled, cost estimated, monitored and controlled.
================================================================
(1) The process of determining, documenting and managing stakeholder needs and requirements to meet project objectives is known as
Plan Scope Management
Collect Requirements
Control Scope
Validate Scope
Answer:B
Hint: See Collect Requirement process definition, Page 105, PMBOK 5
(2) The Scope Management Plan is included in which of the following documents?
Project Management Plan
The Work Breakdown Structure
The Scope Statement
Project Specifications
Answer: A
Hint: Scope Management Plan is a part of Project Management Plan
(3) Project Scope:
is of concern only at the start of the project
is mainly a problem to be handled by the change control procedures during the project execution phase.
Should be managed and controlled from the project concept through closing
is usually not a problem after the contract or other document authorizing the project has been approved.
Answer: C
Hint: Scope Management is done from the start till the closing phase
(4) The Project charter is created by:
The project manager
The sponsor
The Vice President over a functional management group
The customer
Answer:B
Hint: It is created by project sponsor(s)
(5) The project scope statement furnishes the basis for:
clearly defined acceptance criteria
Provides links to the clients functional management groups
Allowing the project to move to the next phase
A way to provide updated information to the accounting department
Answer:A
Hint: See Sec 5.3.3.1, Page 123-24, PMBOK 5
(6) The Scope Baseline is:
the original description of the project's end results
a summary description of the project's original content and end product, including basic budgetary and time constraint data
the original project budget and schedule
a and c
Answer: B
Hint: See, Sec 5.4.3.1, Page 131, PMBOK 5
(7) The Requirements that describe features, functions and characteristics of the product, service, or result that will meet the business and stakeholders requirements is known as:
Solution Requirements
Project Requirements
Transition Requirements
Quality Requirements
Answer: A
Hint: See Sec 5.2, Page 112, PMBOK 5
(8) The PM distributed a document to the stakeholders, which described the software to be developed, the functionality, the users it would serve and the installation timeline. The document was an example of:
Product scope
Project scope
A combination of project and product scope
It was not complete enough to be either a product or a project scope document
Answer: D
Hint: Refer Page 105, PMBOK 5
(9) Each item of the Work Breakdown Structure is assigned a unique identifier. What is the name of this identifier?
Product ID number
Code of account identifier
Quality inspection identifier
Project activity code
Answer: B
Hint: See code of accounts definition, Page 531, PMBOK 5
(10) What is the term for the 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?
Idea/mind mapping
Multicriteria Decision Analysis
Affinity Diagram
Both B& C
Answer: B
Hint: See Multi-Criteria Decision Analysis definition, Page 531, PMBOK 5
(11) What is the term used for the processes required to ensure that the project include all the work required, and only the work required, to complete the work successfully.
Project Scope Management
Bill of Materials
Work Breakdown Structure
None of the above
Answer: A
Hint: See Project Scope Management definition, Page 555, PMBOK 5
(12) Project Scope Management has following processes:
a. Collect Requirements
b. Plan Scope management
c. Define Scope
d. Create WBS
Arrange them in the correct sequence.
a-b-c-d
c-d-b-a
b-a-c-d
a-c-b-d
Answer: C
Hint: See Page 106, PMBOK 5
(13) In the context of a project, the term scope refer to
Product Scope
Project Scope
Both A & B
None of the above
Answer: C
Hint: See Page 105, PMBOK 5
(14) 14. A project manager working on the Project Scope Management processes is operating at the Plan Scope Management process, where he is using all of the following inputs excluding
Project Charter
Project Management Plan
EEF
Requirements Documentation
Answer: D
Hint: See Plan Scope Management inputs, Page 106, PMBOK 5
(15) Which of the following inputs used in the process of Collect Requirements is not the output of the preceding process of Plan Scope Management?
Scope Management Plan
Requirement Management Plan
Stakeholder Register
None of the above
Answer: C
Hint: Stakeholder Register is an output of Identify Stakeholders process
(16) The various tools and techniques used during the process of Collect Requirements include all but
Prototypes
Variance Analysis
Benchmarking
Document Analysis
Answer: B
Hint: Variance analysis in not applicable to scope management
(17) Which of the following is not used as an input for the Validate Scope process?
Scope Baseline
Verified Deliverables
Project Management Plan
Work Performance Data
Answer: A
Hint: See Validate Scope process, Page 106, PMBOK 5
(18) Decomposition is an important tool used to
Control Scope
Define Scope
Validate Scope
Create WBS
Answer: D
Hint: See Create WBS process, Page 106, PMBOK 5
(19) The focused sessions that bring key stakeholders together to define product requirements is known as
Interviews
Focus Groups
Facilitated Workshops
None of the above
Answer: C
Hint: See Facilitated Workshops definition, Page 114, PMBOK 5
(20) A grid that links product requirements from their origin to the deliverables that satisfy them is known as
Context Diagrams
Affinity Diagram
Requirements Traceability Matrix
None of the above
Answer: C
================================================================
The project scope management plan, as a component of the project management plan, includes which of the following?
A Preparation of a detailed project scope statement B Creation of the work breakdown structure (WBS) C Specifications for formal verification and acceptance of completed project deliverables D All of the aboveYou are creating your WBS and find that you keep decomposing tasks into smaller and smaller units. How can you tell when you are done?
A Keep decomposing tasks until you reach an amount of work that is small enough to reliably estimate required resources and duration. B Keep decomposing tasks until you reach an amount of work that can be accomplished in one hour. C Keep decomposing work until you reach an amount of work that can be accomplished in your organization’s basic work unit. D Keep decomposing work until you reach a predetermined number of hierarchy levels to keep the WBS balanced.Which of the following is a valid input to the collect requirements process?
A Project charter B Requirements traceability matrix C Validated deliverables D Work performance informationAnswers
Answer D is the best response. The project scope management plan includes preparation of a detailed project scope statement, creation of the WBS, and a process specifying how formal verification and acceptance of the completed project deliverables will be obtained.
Answer A is correct. A properly sized work package is one that is small enough to allow for reliable estimates for required resources and duration. Answers B, C, and D are incorrect because they assume that you are working toward some artificial target that does not contribute to appropriately sized work packages.
Answer A is correct. The project charter is one of two defined inputs for the collect requirements process. (The other input is the stakeholder register.) Answer B is incorrect because the requirements traceability matrix is an output for the collect requirements process. Answers C and D are incorrect because they refer to inputs from other processes.
========================================================================================
As project manager, you are about to start the define scope process. You have the project charter and the organizational process assets list. Because there are no change requests in your project at this point, what must you have before you begin?
A Product analysis
B Requirements documentation
C Updates to project documents
D WBS
What does a project scope statement document?
A What work is to be completed during the project
B What deliverables need to be produced by the project
C Both A and B
D Neither A nor B
The work breakdown structure (WBS) does all of the following except
A Organizes and defines the entire scope of the project
B Divides the project into smaller, more manageable tasks
C Serves as a high-level planning tool for work planned but not yet approved
D Both A and B
Which of the following is an output of the collect requirements process?
A Scope management plan
B Requirements management plan
C Requirements risk breakdown
D Requirements traceability matrix
Answer B is correct. The requirements documentation is an input you need before starting the define scope process. Answer A is incorrect because product analysis is a tool and technique of define scope, not an input. Answer C is incorrect because project document updates are an output, not an input. Answer D is incorrect because the WBS is created in a subsequent process and is not available at this point. Know your inputs, tools and techniques, and outputs of all processes.
========================================================================================
As project manager, you are about to start the define scope process. You have the project charter and the organizational process assets list. Because there are no change requests in your project at this point, what must you have before you begin?
A Product analysis B Requirements documentation C Updates to project documents D WBSWhat does a project scope statement document?
A What work is to be completed during the project B What deliverables need to be produced by the project C Both A and B D Neither A nor BThe work breakdown structure (WBS) does all of the following except
A Organizes and defines the entire scope of the project B Divides the project into smaller, more manageable tasks C Serves as a high-level planning tool for work planned but not yet approved D Both A and BWhich of the following is an output of the collect requirements process?
A Scope management plan B Requirements management plan C Requirements risk breakdown D Requirements traceability matrixAnswer B is correct. The requirements documentation is an input you need before starting the define scope process. Answer A is incorrect because product analysis is a tool and technique of define scope, not an input. Answer C is incorrect because project document updates are an output, not an input. Answer D is incorrect because the WBS is created in a subsequent process and is not available at this point. Know your inputs, tools and techniques, and outputs of all processes.
Answer C is the best response. A project scope statement documents what work is to be accomplished and which deliverables need to be produced. Answers A and B are both individually correct, but Answer C is the better response. Answer D is incorrect.
Answer C is the correct response. The WBS provides a detailed definition of work specified in the current, approved project scope statement. Both Answers A and B describe the WBS and are therefore incorrect responses to the question.
Answer C is the correct response. The WBS provides a detailed definition of work specified in the current, approved project scope statement. Both Answers A and B describe the WBS and are therefore incorrect responses to the question.
Answer D is the correct response. Answers A and B are incorrect because these are outputs of the plan scope management process. Answer C is incorrect because there is no such defined output as a requirements risk breakdown.
===========================================================================
You are a project manager of a large project and you are identifying some alternative techniques to generate different approaches to execute and perform the work of a project. You are doing it as a part of:
1.Collect Requirements
2.Control Scope
3.Verify Scope
4.Define Scope
Correct Answers are : 4
Explanation :
D is the correct answer.
This is call an Alternative Identification in the Define Scope process.
You are a project manager and the project is to install ACs into hotel rooms. You did project cost and time estimates and informed the customer that the project estimates will be accurate if the requirements such as wooden coating are met. This is an example of which of the following?
1.Risk
2.Assumption
3.Constraint
4.Budget analysis
Correct Answers are : 2
Explanation :
B is the correct answer.
This is an example of assumption because estimates provided will be accurate if the rooms meet the requirements like (wooden coated). A and C are incorrect because the scenario did not describe a risk or constraint.
You are the project manager for a project to create a new product for the marketing industry. You recently came to know that a competitor is also working on a similar project with an additional web-based tool, which your project does not offer. You initiate a change request to update your project. This is an example of:
1.A change due to an external event
2.A change due to an error and omission in the initiation phase
3.A change due to an error or omission in the planning phase
4.A change due to a legal issue
Correct Answers are : 1
Explanation :
A is the correct answer.
The change is requested to remain competitive with the competition an external event.
You are a project manager of a pharmaceutical company. A new pharmaceutical regulation is passed that changes your project scope. For the project to be in accordance with the new regulation, what should be your next action?
1.Present the change to the Change Control Board (CCB)
2.Notify Management
3.Prepare a new baseline to reflect the changes
4.No need to do anything
Correct Answers are : 1
Explanation :
A is the correct answer.
You must present the change to the Change Control Board (CCB) for new changes.
=================================================================
01. All of the following are true about the project scope management plan EXCEPT:
A. It provides guidance on how project scope will be defined, documented, managed, and controlled.
B. It provides guidance on how project scope will be verified.
C. It may be formal or informal, highly detailed, or broadly framed, based upon the needs of the project.
D. It is separate from the project management plan.
02. Collect Requirements is the process of defining and documenting stakeholders’ needs to meet the project objectives. All of the following are true about this process EXCEPT:
A. The project’s success is directly influenced by the care taken in capturing and managing project and product requirements.
B. Requirements include the quantified and documented needs and expectations of the sponsor, customer, and other stakeholders.
C. Requirements become the foundation of the WBS. Cost, schedule, and quality planning are all built upon these requirements.
D. The development of requirements begins with an analysis of the information contained in the risk register.
03. All of the following are true about the project scope statement EXCEPT:
A. It is an output of the Verify Scope process.
B. It describes, in detail, the project’s deliverables and the work required to create those deliverables.
C. It provides a common understanding of the project scope among project stakeholders.
D. It may contain explicit scope exclusions that can assist in managing stakeholder expectations.
04. All of the following are true about the Control Scope process EXCEPT:
A. Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline.
B. Project scope control is used to manage the actual changes when they occur and is integrated with the other control processes.
C. Scope changes can be avoided by developing clear and concise specifications and enforcing strict adherence to them.
D. Scope control includes determining the cause and degree of variance relative to the scope baseline and deciding whether corrective or preventive action is required.
05. Which of the following statements is true about the work breakdown structure (WBS)?
A. The WBS is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables.
B. The WBS is an unstructured list of project activities in chart form.
C. The WBS is the same as the organizational breakdown structure (OBS).
D. The WBS is the bill of materials (BOM) needed to accomplish the project objectives and create the required deliverables.
06. The following is an example of a constraint associated with the project scope that limits the team’s options in scope definition:
A. A predefined budget.
B. The threat of a strike by a subcontractor.
C. Existing relationships with sellers, suppliers, or others in the supply chain.
D. The method used to measure project performance.
07. An input to the Define Scope process is:
A. The type of contract detail language.
B. Project Charter.
C. Work breakdown structure (WBS).
D. Decomposition.
08. What is the WBS typically used for?
A. To organize and define the total scope of the project.
B. To identify the logical person to be project sponsor.
C. To define the level of reporting that the seller provides the buyer.
D. As a record of when work elements are assigned to individuals.
09. The following is true about the WBS:
A. The WBS is another term for the bar (Gantt) chart.
B. Each descending level of the WBS represents an increasingly detailed definition of the project work.
C. Work not in the WBS is usually defined in the scope statement of the project.
D. The WBS shows only the critical path activities.
10. An output of the Define Scope process is:
A. Work breakdown structure (WBS).
B. Resource breakdown structure (RBS).
C. Project scope statement.
D. Scope and schedule delays control plan.
11. Which of the following is true about the Verify Scope process?
A. It is the process of formalizing acceptance of the completed project deliverables.
B. Is not necessary if the project completes on time and within budget.
C. Occurs primarily when revisions or changes are made to project scope.
D. Scope verification is primarily concerned with correctness of the deliverables, while quality control is primarily concerned with acceptance of the deliverables and meeting the quality requirements specified for the deliverables.
12. Which of the following is not an output of the Control Scope process?
A. Work performance measurements.
B. Change requests.
C. Project document updates.
D. Accepted deliverables.
Result Time..!🙂
01. Answer: D. PMBOKâ Guide, page 104, Introduction; and page 126, Section 5.5.1.1
Although not shown here as a discrete process, the work involved in performing the five processes of Project Scope Management is preceded by a planning effort by the project management team. This planning effort is part of the Develop Project Management Plan process (Section 4.2), which produces a scope management plan that provides guidance on how project scope will be defined, documented, verified, managed, and controlled. The scope management plan may be formal or informal, highly detailed, or broadly framed, based upon the needs of the project.
02. Answer: D. PMBOKâ Guide, page 105, Section 5.1
Collect Requirements is the process of defining and documenting stakeholders’ needs to meet the project objectives. The project’s success is directly influenced by the care taken in capturing and managing project and product requirements. Requirements include the quantified and documented needs and expectations of the sponsor, customer, and other stakeholders. These requirements need to be elicited, analyzed, and recorded in enough detail to be measured once project execution begins. Collecting requirements is defining and managing customer expectations. Requirements become the foundation of the WBS. Cost, schedule, and quality planning are all built upon these requirements. The development of requirements begins with an analysis of the information contained in the project charter (Section 4.1.3.1) and the stakeholder register (Section 10.1.3.1).
03. Answer: A. PMBOKâ Guide, page 115, Section 5.2.3.1
The project scope statement describes, in detail, the project’s deliverables and the work required to create those deliverables. The project scope statement also provides a common understanding of the project scope among project stakeholders. It may contain explicit scope exclusions that can assist in managing stakeholder expectations. It enables the project team to perform more detailed planning, guides the project team’s work during execution, and provides the baseline for evaluating whether requests for changes or additional work are contained within or outside the project’s boundaries.
04. Answer: C. PMBOKâ Guide, page 125, Section 5.5; and page 127, Section 5.5.2.1
Control Scope: Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. Controlling the project scope ensures all requested changes and recommended corrective or preventive actions are processed through the Perform Integrated Change Control process (see Section 4.5). Project scope control is also used to manage the actual changes when they occur and is integrated with the other control processes. Uncontrolled changes are often referred to as project scope creep. Change is inevitable, thereby mandating some type of change control process.
Variance Analysis: Project performance measurements are used to assess the magnitude of variation from the original scope baseline. Important aspects of project scope control include determining the cause and degree of variance relative to the scope baseline (Section 5.3.3.3) and deciding whether corrective or preventive action is required.
05. Answer: A. PMBOKâ Guide, page 116, Section 5.3
Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components. The work breakdown structure (WBS) is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables, with each descending level of the WBS representing an increasingly detailed definition of the project work. The WBS organizes and defines the total scope of the project, and represents the work specified in the current approved project scope statement.
06. Answer: A. PMBOKâ Guide, page 115, Section 5.2.3.1
Lists and describes the specific project constraints associated with the project scope that limits the team’s options, for example, a predefined budget or any imposed dates or schedule milestones that are issued by the customer or performing organization. When a project is performed under contract, contractual provisions will generally be constraints. Information on constraints may be listed in the project scope statement or in a separate log.
07. Answer: B. PMBOKâ Guide, page 112, Figure 5-4; and page 112, Section 5.2.1
Project Charter, Requirements Documentation , Organizational Process Assets
08. Answer: A. PMBOKâ Guide, page 116, Section 5.3
Refer Answer 05.
09. Answer: B. PMBOKâ Guide, page 116, Section 5.3
Refer Answer 05.
10. Answer: C. PMBOKâ Guide page 112, Figure 5-4; and pages 115–116, Section 5.2.3
Project Scope Statement, Project Document Updates
11. Answer: A. PMBOKâ Guide, page 123, Section 5.4
Verify Scope is the process of formalizing acceptance of the completed project deliverables. Verifying scope includes reviewing deliverables with the customer or sponsor to ensure that they are completed satisfactorily and obtaining formal acceptance of deliverables by the customer or sponsor. Scope verification differs from quality control in that scope verification is primarily concerned with acceptance of the deliverables, while quality control is primarily concerned with correctness of the deliverables and meeting the quality requirements specified for the deliverables. Quality control is generally performed before scope verification, but these two processes can be performed in parallel.
12. Answer: D. PMBOKâ Guide, page 125, Figure 5-13; page 128, Section 5.5.3; page 123, Figure 5-11; and page 125, Section 5.4.3
Control Scope: Outputs: Work Performance Measurements, Organizational Process Assets Updates , Change Requests, Project Management Plan Updates, Project Document Updates
Accepted Deliverables is an output of Verify Scope process.
===========================================================================
You are a project manager of a large project and you are identifying some alternative techniques to generate different approaches to execute and perform the work of a project. You are doing it as a part of:
1.Collect Requirements
2.Control Scope
3.Verify Scope
4.Define Scope
Correct Answers are : 4
Explanation :
D is the correct answer.
This is call an Alternative Identification in the Define Scope process.
You are a project manager and the project is to install ACs into hotel rooms. You did project cost and time estimates and informed the customer that the project estimates will be accurate if the requirements such as wooden coating are met. This is an example of which of the following?
1.Risk
2.Assumption
3.Constraint
4.Budget analysis
Correct Answers are : 2
Explanation :
B is the correct answer.
This is an example of assumption because estimates provided will be accurate if the rooms meet the requirements like (wooden coated). A and C are incorrect because the scenario did not describe a risk or constraint.
You are the project manager for a project to create a new product for the marketing industry. You recently came to know that a competitor is also working on a similar project with an additional web-based tool, which your project does not offer. You initiate a change request to update your project. This is an example of:
1.A change due to an external event
2.A change due to an error and omission in the initiation phase
3.A change due to an error or omission in the planning phase
4.A change due to a legal issue
Correct Answers are : 1
Explanation :
A is the correct answer.
The change is requested to remain competitive with the competition an external event.
You are a project manager of a pharmaceutical company. A new pharmaceutical regulation is passed that changes your project scope. For the project to be in accordance with the new regulation, what should be your next action?
1.Present the change to the Change Control Board (CCB)
2.Notify Management
3.Prepare a new baseline to reflect the changes
4.No need to do anything
Correct Answers are : 1
Explanation :
A is the correct answer.
You must present the change to the Change Control Board (CCB) for new changes.
=================================================================
01. All of the following are true about the project scope management plan EXCEPT:
A. It provides guidance on how project scope will be defined, documented, managed, and controlled.
B. It provides guidance on how project scope will be verified.
C. It may be formal or informal, highly detailed, or broadly framed, based upon the needs of the project.
D. It is separate from the project management plan.
02. Collect Requirements is the process of defining and documenting stakeholders’ needs to meet the project objectives. All of the following are true about this process EXCEPT:
A. The project’s success is directly influenced by the care taken in capturing and managing project and product requirements.
B. Requirements include the quantified and documented needs and expectations of the sponsor, customer, and other stakeholders.
C. Requirements become the foundation of the WBS. Cost, schedule, and quality planning are all built upon these requirements.
D. The development of requirements begins with an analysis of the information contained in the risk register.
03. All of the following are true about the project scope statement EXCEPT:
A. It is an output of the Verify Scope process.
B. It describes, in detail, the project’s deliverables and the work required to create those deliverables.
C. It provides a common understanding of the project scope among project stakeholders.
D. It may contain explicit scope exclusions that can assist in managing stakeholder expectations.
04. All of the following are true about the Control Scope process EXCEPT:
A. Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline.
B. Project scope control is used to manage the actual changes when they occur and is integrated with the other control processes.
C. Scope changes can be avoided by developing clear and concise specifications and enforcing strict adherence to them.
D. Scope control includes determining the cause and degree of variance relative to the scope baseline and deciding whether corrective or preventive action is required.
05. Which of the following statements is true about the work breakdown structure (WBS)?
A. The WBS is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables.
B. The WBS is an unstructured list of project activities in chart form.
C. The WBS is the same as the organizational breakdown structure (OBS).
D. The WBS is the bill of materials (BOM) needed to accomplish the project objectives and create the required deliverables.
06. The following is an example of a constraint associated with the project scope that limits the team’s options in scope definition:
A. A predefined budget.
B. The threat of a strike by a subcontractor.
C. Existing relationships with sellers, suppliers, or others in the supply chain.
D. The method used to measure project performance.
07. An input to the Define Scope process is:
A. The type of contract detail language.
B. Project Charter.
C. Work breakdown structure (WBS).
D. Decomposition.
08. What is the WBS typically used for?
A. To organize and define the total scope of the project.
B. To identify the logical person to be project sponsor.
C. To define the level of reporting that the seller provides the buyer.
D. As a record of when work elements are assigned to individuals.
09. The following is true about the WBS:
A. The WBS is another term for the bar (Gantt) chart.
B. Each descending level of the WBS represents an increasingly detailed definition of the project work.
C. Work not in the WBS is usually defined in the scope statement of the project.
D. The WBS shows only the critical path activities.
10. An output of the Define Scope process is:
A. Work breakdown structure (WBS).
B. Resource breakdown structure (RBS).
C. Project scope statement.
D. Scope and schedule delays control plan.
11. Which of the following is true about the Verify Scope process?
A. It is the process of formalizing acceptance of the completed project deliverables.
B. Is not necessary if the project completes on time and within budget.
C. Occurs primarily when revisions or changes are made to project scope.
D. Scope verification is primarily concerned with correctness of the deliverables, while quality control is primarily concerned with acceptance of the deliverables and meeting the quality requirements specified for the deliverables.
12. Which of the following is not an output of the Control Scope process?
A. Work performance measurements.
B. Change requests.
C. Project document updates.
D. Accepted deliverables.
Result Time..!🙂
01. Answer: D. PMBOKâ Guide, page 104, Introduction; and page 126, Section 5.5.1.1
Although not shown here as a discrete process, the work involved in performing the five processes of Project Scope Management is preceded by a planning effort by the project management team. This planning effort is part of the Develop Project Management Plan process (Section 4.2), which produces a scope management plan that provides guidance on how project scope will be defined, documented, verified, managed, and controlled. The scope management plan may be formal or informal, highly detailed, or broadly framed, based upon the needs of the project.
02. Answer: D. PMBOKâ Guide, page 105, Section 5.1
Collect Requirements is the process of defining and documenting stakeholders’ needs to meet the project objectives. The project’s success is directly influenced by the care taken in capturing and managing project and product requirements. Requirements include the quantified and documented needs and expectations of the sponsor, customer, and other stakeholders. These requirements need to be elicited, analyzed, and recorded in enough detail to be measured once project execution begins. Collecting requirements is defining and managing customer expectations. Requirements become the foundation of the WBS. Cost, schedule, and quality planning are all built upon these requirements. The development of requirements begins with an analysis of the information contained in the project charter (Section 4.1.3.1) and the stakeholder register (Section 10.1.3.1).
03. Answer: A. PMBOKâ Guide, page 115, Section 5.2.3.1
The project scope statement describes, in detail, the project’s deliverables and the work required to create those deliverables. The project scope statement also provides a common understanding of the project scope among project stakeholders. It may contain explicit scope exclusions that can assist in managing stakeholder expectations. It enables the project team to perform more detailed planning, guides the project team’s work during execution, and provides the baseline for evaluating whether requests for changes or additional work are contained within or outside the project’s boundaries.
04. Answer: C. PMBOKâ Guide, page 125, Section 5.5; and page 127, Section 5.5.2.1
Control Scope: Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. Controlling the project scope ensures all requested changes and recommended corrective or preventive actions are processed through the Perform Integrated Change Control process (see Section 4.5). Project scope control is also used to manage the actual changes when they occur and is integrated with the other control processes. Uncontrolled changes are often referred to as project scope creep. Change is inevitable, thereby mandating some type of change control process.
Variance Analysis: Project performance measurements are used to assess the magnitude of variation from the original scope baseline. Important aspects of project scope control include determining the cause and degree of variance relative to the scope baseline (Section 5.3.3.3) and deciding whether corrective or preventive action is required.
05. Answer: A. PMBOKâ Guide, page 116, Section 5.3
Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components. The work breakdown structure (WBS) is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables, with each descending level of the WBS representing an increasingly detailed definition of the project work. The WBS organizes and defines the total scope of the project, and represents the work specified in the current approved project scope statement.
06. Answer: A. PMBOKâ Guide, page 115, Section 5.2.3.1
Lists and describes the specific project constraints associated with the project scope that limits the team’s options, for example, a predefined budget or any imposed dates or schedule milestones that are issued by the customer or performing organization. When a project is performed under contract, contractual provisions will generally be constraints. Information on constraints may be listed in the project scope statement or in a separate log.
07. Answer: B. PMBOKâ Guide, page 112, Figure 5-4; and page 112, Section 5.2.1
Project Charter, Requirements Documentation , Organizational Process Assets
08. Answer: A. PMBOKâ Guide, page 116, Section 5.3
Refer Answer 05.
09. Answer: B. PMBOKâ Guide, page 116, Section 5.3
Refer Answer 05.
10. Answer: C. PMBOKâ Guide page 112, Figure 5-4; and pages 115–116, Section 5.2.3
Project Scope Statement, Project Document Updates
11. Answer: A. PMBOKâ Guide, page 123, Section 5.4
Verify Scope is the process of formalizing acceptance of the completed project deliverables. Verifying scope includes reviewing deliverables with the customer or sponsor to ensure that they are completed satisfactorily and obtaining formal acceptance of deliverables by the customer or sponsor. Scope verification differs from quality control in that scope verification is primarily concerned with acceptance of the deliverables, while quality control is primarily concerned with correctness of the deliverables and meeting the quality requirements specified for the deliverables. Quality control is generally performed before scope verification, but these two processes can be performed in parallel.
12. Answer: D. PMBOKâ Guide, page 125, Figure 5-13; page 128, Section 5.5.3; page 123, Figure 5-11; and page 125, Section 5.4.3
Control Scope: Outputs: Work Performance Measurements, Organizational Process Assets Updates , Change Requests, Project Management Plan Updates, Project Document Updates
Accepted Deliverables is an output of Verify Scope process.
No comments:
Post a Comment