Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
61 Cards in this Set
- Front
- Back
|
DefinePROJECT SCOPE MANAGEMENT?
(Approved) |
Itincludes the following processes required to ensure that the project includesALL THE WORK required, and ONLY THE WORK required, to complete the projectsuccessfully.
1. Plan Scope Management. 2. Collect Requirements. 3. Define Scope. 4. Create WBS. 5. Validate Scope. 6. Control Scope.
We are primarily concerned with defining what is and what is not included int he project. |
|
|
Whatis Product scope? (Approved) |
- Features and functions that characterize a product, service, or result.
- Measured against the requirement. |
|
|
Whatis Project scope? (Approved) |
- Work needed to deliver a product, service, or result as defined in product scope.
- Measured against the plan. |
|
|
Howis Project Scope different from Product Scope? |
Projectscope is the WORK that must be done to deliver a product with the specifiedfeatures and functions.
Product scope is the features and functions thatcharacterize a product or service. |
|
|
Howis Completion of scope measured? |
- Completionof the project scope is measured against the project management plan.- Completion of the product scope is measuredagainst the product requirements.
So, clearly, product requirements are a keydriver in project scope, and are the starting point for our scope work. |
|
|
Define PLAN SCOPE MANAGEMENT? (Approved) |
Creating a scope management plan that documents how the project scope will be defined, validated, and controlled. |
|
|
What is the key benefit of plan scope management? (Approved) |
It provides guidance and direction on how scope will be managed throughout the project |
|
|
What are the INPUTS for plan scope management? (Approved) |
Project management plan Project charter Enterprise environmental factors Organizational process assets |
|
|
What are the necessary TOOL & TECHNIQUES for plan scope management? (Approved) |
Expert judgment Meetings
|
|
|
What are the OUTPUTS of plan scope management? (Approved) |
Scope management plan Requirements management plan |
|
|
OUTPUT: Define scope management plan? (Approved) |
- A component of the project or program management plan that describes how the scope will be defined, developed, monitored, control, and verified. - The scope management plan is a major input into the Develop Project Management Plan process, and the other scope management processes. |
|
|
OUTPUT: What are the components of a Scope Management Plan? (Approved) |
- Process for preparing a project scope statement. - Process that enables the creation of the WBS from the detailed project scope statement. - Process that establish how the WBS will be maintained and approved - Process that specifies how formal acceptance of the complete deliverables will be obtained - Process to control how request for changes to the detailed project scope statement will be processed. This process is directly linked to the Perform Integrated Change Control process. |
|
|
OUTPUT: What is a requirements management plan? (Approved) |
A component of the project or program management plan that describes how requirements will be analyzed, documented, and managed. Components can include (but no limited to): - How requirements activities will be planned, tracked, and reported. - Configuration management activities such as changes to product. - Requirements prioritization process. - Product metrics that will be used and rationale for using them. - Traceability structure to reflect how requirement attributes will be captured on the traceability matrix. |
|
|
What is the process called COLLECT REQUIREMENTS? (Approved) |
Determining, documenting, and managing stakeholder needs and requirements to meet project objectives. Note: - Helps manage expectations. Form planning and estimating foundations. - There are project and product requirements. |
|
|
What is the key benefit of the process called collect requirements? (Approved) |
It provides the basis for defining and managing the project scope including product scope
Note: - Product scope includes the features and functions that characterize a product, service, or result. |
|
|
What are the INPUTS to the process called collect requirements? (Approved) |
1. Scope management plan. 2. Requirements management plan. 3. Stakeholder management plan. 4. Project charter. 5. Stakeholder register. |
|
|
What are the necessary TOOLS AND TECHNIQUES for collecting requirements?
(Approved) |
1. Interviews. 2. Focus groups. 3. Facilitated workshops. 4. Group creativity techniques. 5. Group decision-making techniques. 6. Questionnaires and surveys. 7. Observations. 8. Prototypes. 9. Benchmarking. 10. Context diagrams. 11. Document analysis. |
|
|
What are the OUTPUTS of the process called collect requirements? (Approved) |
1. Requirements documentation. 2. Requirements traceability matrix. |
|
|
INPUTS: What is a stakeholder register? (113) |
It is a list of stakeholders who can provide information on the requirements
This register also captures the major requirements and main expectations stakeholders may have for the project |
|
|
OUTPUTS: What are the requirements of a project? (112) |
Requirements include conditions or capabilities that are to be met by the project or present in the product, service or result to satisfy an agreement
Requirements include the needs and expectations of the sponsor, customer, and other stakeholders
Requirements become the foundation of the work breakdown structure (WBS) |
|
|
OUTPUTS: Explain requirements documentation?
(Approved and question in the test) |
1. Describes how individual requirements meet the business for the project.
2. Components can included (but not limited to): - Business requirements. - Stakeholder requirements. - Solution requirements. - Project requirements. - Transition requirements - Requirements assumptions, dependencies and constraints. |
|
|
OUTPUTS: What is a requirements traceability matrix? (Approved) |
1. It is a grid that links product requirements from their origin to the deliverables that satisfy them.
2. It provides: - Means to track requirements throughout the project life cycle. - Mechanisms for integrated change control and configuration management. |
|
|
TOOLS AND TECHNIQUES: What is the purpose of a facilitated workshop? (114) |
It is a focused session that brings key stakeholders together to define product requirements
It is more intense than a focus group which is meant to discover expectations and attitudes about a proposed product, service, or result |
|
|
TOOLS AND TECHNIQUES: What are some group creativity techniques that can be used to identify project and product requirements? (115) |
Brainstorming Nominal group technique Idea/mind mapping Affinity diagram Multi-criteria decision analysis |
|
|
TOOLS AND TECHNIQUES: What are some group decision-making techniques that can be used to generate, classify, and prioritize product requirements? (115) |
Unanimity Majority Plurality Dictatorship |
|
|
TOOLS AND TECHNIQUES: What is a prototype? (116) |
A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it |
|
|
TOOLS AND TECHNIQUES: What is benchmarking? (116) |
Comparing 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 |
|
|
TOOLS AND TECHNIQUES: What is a context diagram? (117) |
It is a model that visually depicts the product scope by showing a business system and how people and other systems interact with it |
|
|
What does it mean to DEFINE SCOPE? (Approved) |
Developing a detailed description of the project and product |
|
|
What is the key benefit of defining scope? (Approved) |
It describes the product, service, or result boundaries by defining which of the requirements collected will be included in and excluded from the project scope. |
|
|
What are the INPUTS to defining scope? (Approved) |
1. Scope management plan. 2. Project charter. 3. Requirements documentation. 4. Organizational process assets. |
|
|
What are the TOOLS AND TECHNIQUES necessary for defining scope? (Approved) |
1. Expert judgment. 2. Product analysis. 3. Alternatives generation. 4. Facilitated workshops. |
|
|
What are the OUTPUTS of Define scope? (Approved) |
1. Project scope statement. 2. Project document update. |
|
|
OUTPUTS: What is a project scope statement? (Approved) |
- Description of the project scope, major deliverables, assumptions, and constraints. - Document the entire scope including project and product scope. - Describes in detail project deliverables and required work. - Provides document basis for making future projects decision and for conforming or developing a common understanding of project scope among the stakeholders. |
|
|
OUTPUTS: What are the elements of a project scope statement ? (Approved) |
- Product scope description (which is progressively elaborated). - Acceptance criteria. - Deliverable. - Project exclusion. - Constraints. - Assumptions. Note: All this is used to manage expectations |
|
|
What is the difference between a project charter and a project scope statement? (124) |
The project charter contains high-level information, while the project scope statement contains a detailed description of the scope elements |
|
|
What does it mean to CREATE WBS? (Approved) |
Subdividing project deliverables and project work into smaller, more manageable components
|
|
|
What is the key benefit of create WBS? (Approved) |
It provides a structured vision of what has to be delivered. |
|
|
What are the inputs to creating WBS? (Approved) |
1. Scope management plan. 2. Project scope statement. 3. Requirements documentation. 4. Enterprise environmental factors. 4. Organizational process assets. |
|
|
What are the necessary TOOLS AND TECHNIQUES for creating WBS? (Approved) |
1. Decomposition. 2. Expert judgment. |
|
|
What is the OUTPUTS from creating WBS? (Approved) |
1. Scope baselines. 2. Project documents updates.
|
|
|
TOOLS AND TECHNIQUES: What is decomposition? (Approved) |
1. It is a technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts called work packages. 2. Level guides by the degree of control needed using: A. Rolling wave planning: It is a iterative planning technique in which work to be accomplished in the near future is planned in detail, while work in the future is planned at a higher level. B. Word package: Work defined at the lowest level of the WBS for which cost and duration can be estimated and managed. |
|
|
OUTPUTS: Explain scope baseline: (Approved) |
1. Approved version of a : - Scope statement (covered previously in define scope). - Work Breakdown Structure. - WBS dictionary 2. Can be change only through formal change control. 3. Used as a basic for comparaison. |
|
|
OUTPUTS: In the Scope baseline explain what is Work breakdown structure or WBS? (Approved)
|
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables |
|
|
OUTPUTS: From scope baseline what are WBS justification? (Approved) |
- Facilitate estimating. - Help in communicating all the work to be delivered to stakeholders. - Allows a better understanding of the product or service to be delivered. - Makes tracking easier. - Simplifies accountability assignment. - Represents the basis for most of the other planning, monitoring and control documents related to the other key knowledge areas. |
|
|
OUTPUTS: From scope baseline, what is a WBS dictionary? (Approved) |
1. A document, which is companion to WBS, that provides detailed deliverable, activity, and scheduling information about each component (work package) in the WBS. 2. May include but not limited to: - Code of account identifier. - Description work. - Responsible organization. - Schedule milestone and activities. - Required resources. - Cost estimates. - Quality requirements and acceptance criteria - Technical references and agreements information. |
|
|
What are some of the approaches to creating a WBS? (129) What is the 100% rule? (131) |
1. Approaches Top-down approach The use of organization-specific guidelines The use of WBS templates. 2.100% rule The total of the work at the lowest levels should roll up to the higher levels so that nothing is left out and no extra work is performed |
|
|
What does it mean to VALIDATE SCOPE? (Approved) |
Formalizing acceptance of the completed project deliverables. Notes: - Includes reviewing deliverables with the customer or sponsor to ensure that they are completed satisfactorily. - Concerned with acceptance while quality whit correctness. |
|
|
What is the key benefit of validating scope? (Approved) |
It brings objectivity to the acceptance process and increases the chance of final product, service, or result acceptance by validating each deliverable. |
|
|
What are the inputs to validating scope? (Approved) |
1. Project management plan. 2. Requirements documentation. 3. Requirements traceability matrix. 3. Verified deliverables. 4. Work performance data. |
|
|
What are the necessary tools for validating scope? (Approved) |
1. Inspection. 2. Group decision-making techniques. |
|
|
What are the outputs from validating scope? (Approved) |
1. Accepted deliverables. 2. Change requests. 3. Work performance information. 3. Project documents updates. |
|
|
How does the validated scope process differ from the control quality process? (134) |
The former 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 |
|
|
TOOLS AND TECHNIQUE: What does inspection entail? (135) |
It includes measuring, examining, and validating whether work and deliverables meet requirements and product acceptance criteria |
|
|
What does it mean to CONTROL SCOPE? (Approved) |
Monitoring the status of the project and product scope and managing changes to the scope baseline. Notes: - Ensures all requested changes and recommended corrective or preventive actions are processed through the Perform Integrated Change Control process. |
|
|
What is the key benefit to controlling scope? (Approved) |
It allows the scope baseline to be maintained throughout the project |
|
|
What are the INPUTS to controlling scope? (Approved) |
1. Project management plan. 2. Requirements documentation. 3. Requirements traceability matrix. 4. Work performance data. 5. Organizational process assets. |
|
|
What are the necessary TOOLS AND TECHNIQUES for controlling scope? (Approved) |
Variance analysis |
|
|
What are the OUTPUTS from controlling scope? (Approved) |
1.Work performance information. 2. Change requests. 3. Project management plan updates. 4. project documents updates. 5. Organizational process assets updates. |
|
|
Mention some sources of Scope changes? (Approved) |
- Clients's changes. - Sponsor's changes. - Design errors. - Unforeseen problems. - Environmental changes. |
|
|
TOOLS AND TECHNIQUES: What is variance analysis? (139) |
A technique for determining the cause and degree of difference between the baseline and actual performance |
