Scope Flashcards
Scope Baseline
Scope Baseline is the approved version of a scope statement, Work Breakdown Structure (WBS) and its associated WBS dictionary. The scope baseline can be changed using formal change control procedures and is used as a basis for comparison to actual results.
Scope Creep
Scope Creep is the uncontrolled expansion of project scope without adjustments to time, cost, and resource plan or estimates.
Scope Management Plan
A Scope Management Plan is a component of the project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and validated.
Scope Statement
A Scope Statement contains details about project deliverables and the major objectives of a project, including measurable outcomes.
You are coaching a project team that has historically struggled with managing their project scopes. You tell the team that managing the project scope is an absolute must for any successful project. What is the MAIN reason for controlling the project scope?
Preventing scope creep by managing approved changes and disregarding rejected changes. This reduces the risk of scope creep on the project.
NOT To prevent changes from affecting the project
The main reason for controlling the project scope is to deal with the impact of changes on the project. [PMBOK7 p87] (Domain: Process, Task 8)
Given that the high-level scope and requirements are understood, you are trying to collect detailed system requirements during the system design phase. What do you do when your stakeholders do not have enough technical background and exposure to similar technologies and are unable to provide you the information you are looking for during system design brainstorming sessions? Without these detailed requirements, you are not able to progress with your system design.
Elicit and validate detailed requirements through prototyping.
NOT Hire a subject matter expert highly skilled in the technology being implemented.
NOR Hire a qualified business analyst to assist you.
NOR Design and develop a minimally viable product.
The issue here is over the ability of the stakeholders to provide detailed requirements during brainstorming sessions. Stakeholders who do not have prior experience in using similar systems often struggle to articulate their requirements. In such situations, prototyping is often used to elicit and validate stakeholder requirements. Hiring an SME or a BA won’t resolve the problem at hand as the scenario doesn’t tell us that the team doesn’t have required elicitation and management skills. [PMBOK7 p83] (Domain: Process, Task 8)
What document should be the source of truth on the scope of a project? It defines the total scope of the project and represents the work specified in the current approved project scope statement?
Work Breakdown Structure (WBS)
NOT Project Charter
The WBS is a hierarchical decomposition of the work to be performed by the project team. It defines the total scope of the project. It represents the work specified in the currently approved project scope statement. [PMBOK7 p84-85] (Domain: Process, Task 8)
You are managing a construction project. When you started the project, the scope of work was not clear and was based on a rather high-level estimate. Now that you are in the middle of the project, more information has become available. As a result, you now need to change some of the key subcontracts on the project. Which of the following will guide you through the change process?
Change control terms of the individual subcontracts
NOT Project management plan’s change control procedures
Your project’s change control procedures are internal to your project, that is, the scope of work directly under your project’s control. Specific contract change control procedures can be found in the individual subcontracts that can be different for each subcontract. [PMBOK7 p66] (Domain: Process, Task 10)
You are a project manager to develop a website for your customers. Some key stakeholders in the project suggested scope changes to improve the website’s look and feel. Your team has analyzed the impact of these changes and presented the analysis to the Change Control Board (CCB) for approval. What should be your next step if the CCB accepts all proposed changes?
Revise cost estimates, schedule dates, resource requirements, and planning documents
NOT Implement the change request and update stakeholders
Approved change requests require changes to cost estimates, resource requirements, schedule dates and activity sequences. You should incorporate these revisions first before asking your team to implement the changes. Stakeholders can be updated after making the changes. Therefore, your first step is revising the estimates and baselines. [PMBOK7 p186-187] (Domain: Process, Task 9)
You are managing a project. Both the client and your project team agree that a number of change requests are expected during the course of the project. Timely and effective project communications are critical for the success of this project. What will allow you to communicate all approved and rejected changes to the stakeholders consistently?
A configuration management system including change control processes
NOT Change management board
A configuration/change management system, including change control processes, provides a mechanism for the project management team to communicate all approved and rejected changes to the stakeholders consistently. [PMBOK7 p17] (Domain: People, Task 9)
Describe the hierarchy of scope management plan, scope baseline, and scope statement.
The scope management plan describes how the scope will be defined, developed, monitored, controlled, and validated. Scope statement defines scope after collecting requirements. WBS refines the requirements further.
These processes inform each other.
Scope baseline is approved including the scope statement, WBS and its unique WBS dictionary.
A client has requested a specification change in a design. The project manager brings the request to the project’s design leader. After reviewing the request’s details, the design leader states there are no experts in this technology in your organization. As a result, your team cannot assess the full impact of the requested change on the project. What should the project manager do?
Hire an outside consultant to provide the necessary expertise to evaluate the request
NOT Consult the sponsor
The project manager’s best option is to hire an outside consultant to provide the necessary expertise to evaluate the request. Once the project manager has a better understanding of the feasibility of the request, he or she can bring it to the project stakeholders for discussion. PMI requires project managers to work within the realm of their experience and skills. Forming a recommendation to accept or reject the change without consulting an expert would be a violation of the PMI code. [PMI Code of Ethics and Professional Conduct] (Domain: Business Environment, Task 1)
Done Drift
Done Drift is when the project goal is constantly moving
Work Package
Work Package is the planned work that is contained within the lowest level of WBS components
Planning package
Planning package is the WBS component below the control account with known work content but without detailed schedule activities.
Control Account
A management control point at which scope, budget, actual cost, and schedule are integrated and compared to earned value for performance measurement. A Control Account aggregates work at higher levels of the WBS for earned value and performance measurement.
Requirements Traceability Matrix
A Requirements Traceability Matrix is a document that links requirements to their origins and tracks their fulfillment throughout the project lifecycle.
Name the Scope Management process steps in sequential order.
Plan Scope Management
Collect Requirements
Define Scope
Create WBS
Validate Scope
Control Scope
Agile Practice Guide, p90, Annex 1
Verified Deliverable
Verified Deliverables have been compared to the scope/requirements and specifications to ensure they are correct.
Verification
The evaluation of whether a product, service, or result complies with a regulation, requirement, specification, or imposed condition. (focus on meeting requirements/specifications) See also “Validation”.
Validation
The assurance that a product, service, or result meets the needs of the customer and other identified stakeholders. (focus on customer/stakeholder approval) See also “Verification”.
Project Scope Statement
The description of the project scope, major deliverables, assumptions, and constraints.
