PMP Exam Prep Ch05

Start Studying!

Terms

undefined, object

copy deck

What's scope management?: Process of defining what work is required and then making sure that all that work and only that work is done.
Is making sure all changes fit within project charter part of Scope Management?: Yes
Does scope management allows extra work or gold plating?: No
Difference between product and project scope: Product is in terms of features and functions that characterize the product, Project is in terms of the work needed to deliver the product with such functions.
Documents that conform the Scope Baseline: Project Scope Statement, WBS and WBS dictionary.
5 scope management processes: Collect Requirements, Define Scope, Create WBS, Verify Scope and Control Scope
Process Groups where Scope management takes place: Planning and Montoring and Controlling.
Describe Scope Project Management Plan: Provides guidance on how scope will be planned,documented, verified, managed and controlled. It may be formal or informal, highly detailed or broadly framed, depending on project needs.
Process where detailed project scope statement is prepared.: Define Scope
What is Define Scope process?: Development of detailed description of the project and product in project scope statement. Existing risks, constraints and assumptions are analyzed for completeness.
Tools and techniques to Define Scope: Expert Judgement
Product Analysis
Alternatives identification
Facilitated workshops
Smaller pieces of WBS or its lowest level.: Work Packages
Description of WBS: Deliverable oriented
Hierarchical decomposition of work.
Includes only work needed to create deliverables.
Defines total scope of the project.
Represents the work specified in project scope statement.
Uses of WBS: Help prevent work from slipping throught the cracks,
provides understanding so it's a buy-in and communication tool with stakeholders, and
provides basis to estimating staff, cost and time.
Foundation of the project, therefore must exist in every project: WBS
Process to create WBS that is the subdivision of deliverables into smaller, more manageable components.: Decomposition
Use of Control Accounts: Not estimating at work package level.
Integrate scope, cost and schedule to compare earned value for performance measurement.
Information included in WBS Dictionary: Code of account identifier,
Description of work, Responsible
Milestones, schedule activities, resources, cost estimates, quality requirements, acceptance criteria, technical references and contract information.
What does Verify Scope need as input?: Validated Deliverables,
Scope Baseline from PM Plan,
Requirements documentation and Requirements traceability matrix
Actions associated to Verify Scope.: Review deliverables with customer to ensure they are completed satisfactorily.
Gain stakeholder's sign-off or acceptance.
Difference between Verify Scope and Quality Control: SV focus in customer acceptance while QC in meeting quality requirements and correctness of work, QC is generally done first.
Describe Scope Control process: PROACTIVE process to control factors that affect scope,
measure and assess their impact against Scope Baseline
to determine UPDATES to project management plan, and RECOMMEND preventive or corrective actions.
Process that assures change requests and corrective or preventive actions are processed through Integrated Change Control: Control Scope
Tools for Control Scope process: Variance Analysis
When a project is about to finish and stakeholders are not satisfied with deliverables, what process could have prevented this?: Not control scope since it's done during monitoring and controlling but Collect Requirements or Define Scope help prevent likelihood of problems.
When Verify Scope is performed?: When deliverables are completed and validated.
Process Group where Collect Requirements process takes place?: Planning
Process Group where Define Scope process takes place?: Planning
Process Group where Create WBS takes place?: Planning
Process Group where Verify Scope takes place?: Monitoring and Controlling
Process Group where Control Scope process takes place?: Monitoring and Controlling
What process results in accepted deliverables?: Verify Scope
Outputs of Verify Scope process: Accepted Deliverables
Change Requests
Project Document Updates.
Decomposition Level of WBS when project is too big to estimate at Work Package Level: Control Accounts
Decomposition of Work Packages: Activities and WBS Dictionary
Does WBS show dependencies among Work Packages?: No
Pieces of WBS break down that can be realistically estimated, meaningful and cannot be logically subdivided further: Work Packages
What process implements the planning effort of Project Scope Management?: Develop Project Management Plan in Project Integration Management
Process of defining and documenting stakeholders' needs to meet project objectives.: Collect Requirements
What are requirements?: Quantified and documented needs, wants and expectations of the sponsor, customer and other stakeholders.
Why are requirements important?: They are the foundation for WBS.
Cost, Schedule, Quality planning are built upon these.
Help to define and manage customer expectations.
What do you need to start collecting requirements: Project Charter
Stakeholder register
Technique to collect requirements that is a formal direct talk usually one-on-one to discover information from stakeholders.: Interviews
Technique that brings together prequalified stakeholders and subject matter experts to learn about expectations and attitudes about a proposed product. It is usually conducted in a conversational manner by a trained moderator.: Focus Group
Group sessions that help to quickly define and reconcile cross-functional requirements.: Facilitated Workshops
Group sessions that help to build trust, relationships, improve communication among stakeholders and increased chances of consensus.: Facilitated Workshops
Group Creativity Techniques used to identify product and project requirements: Brainstorming
Nominal Group (brainstorming plus voting to rank ideas)
Delphi Technique
Idea/mind mapping
Affinity Diagram (sorted large number of ideas)
Technique that adds a voting process to brainstorming: Nominal group technique
Group Creativity Technique where a selected group of experts answer questionnaires and provide feedback to responses from requirement gathering in a anynomous manner.: Delphi Technique
Technique that allows large number of ideas to be sorted into groups for review and analysis: Affinity diagram
Technique that is used to reflect commonalities and differences in understanding of ideas.: Idea/mind mapping
Methods to reach a decision in Group Decision Making technique (Collect Requirements): Unanimity
Majority
Plurality
Dictatorship
Decision making method where largest block decides: Plurality
Method to collect requirements used when audience is broad, a quick turnaround is needed and statistical analysis is appropriate.: Questionnaires and Surveys
Also known as job shadowing used when people have difficulty or are reluctant to articulate requirements.: Observations
Technique to provide a working model of expected product before actually building it.: Prototyping, used in Collect Requirements process
3 outputs from Collecting Requirements: Requirements Documentation
Requirements Management Plan
Requirements Traceability Matrix
Parts of Requirements Management Plan: How requirements will be planned, tracked and reported.
Configuration management, prioritization process,
product metrics and
traceability structure.
Importance of Requirements Traceability Matrix: It links requirements to business and project objectives throughout product life cycle.
It helps to ensure approved requirements are delivered at the end of project.
Processes that use Requirements Traceability Matrix: Control and Verify Scope
Processes that use Requirements Documentation: Define Scope
Create WBS
Verify Scope
Control Scope
Documents used to generate project scope statement in Define Scope Process: Project Charter
Requirements documentation
What documents are updated as result of Define Scope?: Project documents
Define scope tool used to translate high level product description into tangible deliverables.: Product Analysis
Define scope tool used to generate different approaches to execute and perform project work.: Alternative Identification
Uses of Project Scope Statement: Provides common understanding among stakeholders.
Perform detailed planning.
Guides project team's work during execution.
Provides baseline for evaluating changes or additional work
Parts of Project Scope Statement: Product Scope Description
Product Acceptance Criteria
Project Deliverables
Project Exclusions
Project Constraints
Project Assumptions
Output of Define Scope Process that is part of PM plan and includes Project Scope Statement, WBS and WBS Dictionary: Scope Baseline
Only tool used to Verify Scope: Inspection
Process that providesvalidated deliverables to Verify Scope process: Perform Quality Control
What happens with completed deliverables that are not accepted by customer or stakeholder?: Change request for defect repair is submitted to Perform Integrated Change Control.
Inputs from Direct and Manage Project Execution to Control Scope.: Work Performance Information
Uncontrolled changes to scope: Project Scope Creep.
Parts of PM plan used as input of Control Scope process (1 baseline and 4 Mgmt Plans): Scope Baseline
Scope Management Plan
Change Management Plan
Configuration Management Plan
Requirements Management Plan
Information from Collect Requirements used in Control Scope process: Requirements Documentation
Requirements traceability matrix
Updates resulting from Control Scope: OPA
PM Plan
Project Documents
Types of change requests resulting from Control Scope process: Preventive actions
Corrective actions
Defect Repairs
Output from Control Scope that includes variance measurements: Work Performance Measurements
Techniques used for Product Analysis: Product Breakdown
System Analysis
System Engineering
Requirements Analysis
Value Analysis
Value Engineering
Product metrics are part of what document: Requirements Management Plan

Start Studying!

Deck Info

Number of cards 80