Chapter 5: Project Scope Management Flashcards
Which knowledge area includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully:
A. Project Cost Management
B. Project Integration Management
C. Project Scope Management
D. Project Communications Management
C. Project Scope Management
The process of determining, documenting, and managing stakeholder needs and requirements is known as:
A. Collect requirements
B. Define scope
C. Plan scope management
D. Create WBS
A. Collect requirements
When can a scope baseline be changed:
A. As required by the project manager
B. By the project stakeholders
C. Only through formal change control procedures
D. By the project sponsor
C. Only through formal change control procedures
Company SVT is undertaking a project to construct an oil pipeline between Alberta and Texas. They have been working on a document which says how the project scope will be defined, validated and controlled. Which PMBOK process will they use for this:
A. Define Scope
B. Plan Scope Management
C. Validate Scope
D. Collect Requirements
B. Plan Scope Management
Which document is used to provide the project context needed to plan the scope management processes:
A. The Project Charter
B. The Scope Management Plan
C. The Project Management Plan
D. The Project Definition
A. The Project Charter
Which of the following is not a component of a scope management plan:
A. Process that specifies how formal acceptance of the completed project deliverables will be obtained
B. Process that establishes how the WBS will be maintained and approved
C. Process for preparing a detailed project scope statement
D. Process for the development of the project charter
D. Process for the development of the project charter
Which type of project requirements capture any condition or criteria needed to validate the successful completion of a project deliverable or fulfillment of other project requirements:
A. Business requirements
B. Quality requirements
C. Solution requirements
D. Project requirements
B. Quality requirements
Brainstorming, nominal group technique, idea/mind mapping, affinity diagram and multi criteria decision analysis are described in PMBOK as:
A. Group creativity techniques
B. Group meeting techniques
C. Group facilitation techniques
D. Collecting requirements
A. Group creativity techniques
Which of the following is not a group decision making technique:
A. Unanimity
B. Plurality
C. Dictatorship
D. Brainstorming
D. Brainstorming
A grid that links product requirements from their origin to the deliverables that satisfy them is known as:
A. Requirements traceability matrix
B. Product requirements matrix
C. Project requirements matrix
D. Affinity diagram
A. Requirements traceability matrix
Company TAZ Software is designing a new software application. The have a clear vision of what the software will do but are developing the detail of how the software will do this as the project proceeds. They are making short term plans for the project and reviewing these and determining how to proceed next at the end of each stage. This type of project is known as:
A. A waterfall project
B. A highly defined project
C. An iterative life cycle project
D. A multiple phase project
C. An iterative life cycle project
Product breakdown, systems analysis, requirements analysis, systems engineering and value analysis are all techniques that are used in:
A. Alternatives generation
B. Product analysis
C. Facilitated workshops
D. Brainstorming
B. Product analysis
The description of the project scope, major deliverables, assumptions and constraints is known in PMBOK as:
A. The project scope definition
B. The project management plan
C. The project charter
D. The project scope statement
D. The project scope statement
Limiting factors that affect the execution of the project are known in PMBOK as:
A. Project exclusions
B. Project constraints
C. Project limitations
D. Project assumptions
B. Project constraints
The 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 project deliverable is known in PMBOK as:
A. The work breakdown structure
B. Project decomposition
C. Product analysis
D. Alternatives generation
A. The work breakdown structure
The planned work in the lowest level of WBS components are called:
A. Work packages
B. Work tasks
C. Project activities
D. Project requirements
A. Work packages
The document that provides deliverable, activity, and scheduling information about each component in the WBS is:
A. The project schedule
B. The WBS dictionary
C. The WBS register
D. The WBS log
B. The WBS dictionary
The plan which specifies how formal acceptance of the completed project deliverables will be obtained is:
A. The quality management plan
B. The project management plan
C. The scope management plan
D. The risk management plan
C. The scope management plan
Uncontrolled expansion to product or project scope is referred to as:
A. Scope growth
B. Scope wandering
C. Scope enlargement
D. Scope creep
D. Scope creep
The technique that is used to determine the cause and degree of difference between the baseline and actual performance is:
A. Gap analysis
B. Earned value analysis
C. Variance analysis
D. Work performance analysis
C. Variance analysis
Project Scope Management processes
- Plan Scope Management
- Collect Requirements
- Define Scope
- Create WBS
- Validate Scope
- Control Scope
Business analysis
Analysis undertaken before the project starts and before the project manager has been appointed
Plan Scope Management process
Process in which the project manager prepares the Scope Management Plan
Scope Management Plan
Describes how the scope will be managed, including how it will be defined and developed, monitored and controlled, and verified to ensure that it has been successfully achieved; becomes part of the overall project management plan
Plan Scope Management inputs
- Project charter
- Project management plan
- EEFs
- Organizational process assets
- Development approach (adaptive, agile, predictive, etc.)
Plan Scope Management tools and techniques
- Expert judgement
- Data analysis techniques
- Meetings
Alternatives analysis
Data analysis technique that evaluates options for achieving project objectives
Plan Scope Management outputs
- Elements that describes how the scope will be managed
- Requirements management plan
Requirements management plan
Output of the Plan Scope Management process; describes how the project’s detailed requirements will be identified, described, and managed
Collect Requirements process
Process for detailing requirements for the organization in which the project is taking place and also for other stakeholders
Categories of requirements in Collect Requirements process
- Business
- Stakeholder
- Technical
- Solutions
- Transitions
- Project
- Quality
- Others, project-dependent
Collect Requirements inputs
- Project charter
- Project management plan components (scope management, requirements management and stakeholder engagement plans)
- Business documents
- Project agreements
- EEFs
- Organizational process assets
Collect Requirements tools and techniques
- Expert judgement
- Data gathering techniques
- Group creativity techniques
- Group decision making techniques
- Questionnaires and surveys
- Observations of activity
- Prototypes
- Benchmarking
- Context diagrams
- Document analysis
Data gathering techniques
Techniques in the Collect Requirements process, which include interviews, focus groups, and facilitated workshops
Group creativity techniques
Techniques in the Collect Requirements process, which encourage people to think creatively and share idea with each other, such as brainstorming and affinity diagrams
Collect Requirements outputs
Documentation of the requirements of the project
Requirements Traceability Matrix
Links individual requirements to business and project activities; many projects use this to document requirements
Define Scope process
Process for defining project scope and developing project scope statement
Define Scope inputs
- Project charter
- Scope management plan
- Requirements documentation
- Organizational process assets
- EEFs
Define Scope tools and techniques
- Expert judgement
- Product analysis
- Alternatives generation
- Facilitates workshops
Product analysis
Analysis that breaks down requirements from known product characteristics using tools such as systems engineering, value engineering and value analysis
Define Scope outputs
- Project Scope Statement
- Updated project documents
Project Scope Statement
Output of the Define Scope process; provides clarity about the project product and work. It will usually include:
- Details of the product scope
- What is necessary before the deliverables of the project will be accepted as complete
- Project deliverables for each process, phase, and the project itself
- What the project will not do
- Constraints
- Assumptions
Create Work Breakdown Structure process
Process for providing a detailed breakdown of the work that will be done on the project through decomposition of the scope into smaller, manageable activities and, at the lowest level, work packages
Decomposition
Used to breakdown the scope statement into smaller, more manageable activities. It is the breaking down of the project product, service or result into the detailed elements that are combined to create it
Work packages
Term for the work to be done at the lowest level of decomposition in the WBS
Create WBS inputs
- Scope management plan
- Project management plan (project scope management)
- Requirements documentation
- EEFs
- Organizational process assets
Create WBS tools and techniques
- Expert judgement
- Templates
- Decomposition
- Rolling wave planning (for iterative/agile projects)
Create WBS outputs
- Scope baseline
- WBS dictionary
- Project document updates
Scope baseline
A document which includes the scope statement, WBS, work packages, and (possibly) planning packages
Work breakdown structure (WBS) dictionary
Provides details of each WBS component
Validate Scope process
Formal process of meeting with the project client or sponsor to review project deliverables and decide on whether they have been completed satisfactorily; focused on the acceptance of the deliverables by the client or sponsor
Validate Scope inputs
- Project management plan
- Scope baseline
- Project documentation (lessons learned register and quality reports)
- Requirement traceability matrix
- Verified deliverables from the Control Quality process
Validate Scope tools and techniques
- Formal inspection Process (audits, walkthroughs, reviews, etc.)
- Group decision making techniques
Validate Scope outputs
- Accepted deliverables (possibly with formal signatures)
- Change requests
- Work performance information
- Updated project documentation
Control Scope process
Process for monitoring project activity to understand if it is proceeding according to the scope baseline and allowing any changes to be made in a structured way; intended to prevent scope creep
Scope creep
Uncontrolled changes to project scope that will increase project cost and time
Control Scope inputs
- Project management plan elements (scope baseline and scope, change, configuration and requirements management plans)
- Project documentation
- Work performance data
- Organizational process assets
Control Scope tools and techniques
- Variance analysis
- Other analysis techniques
Variance analysis
Analysis used to understand the amount and causes of variance and whether action is needed to deal with it
Control Scope outputs
- Work performance information
- Change requests
- Project management plan updates
- Other project document updates
- Organizational process assets updates
Example EEFs that are inputs to the Plan Scope Management process
- Organizational culture
- Market conditions
- Labour availability
Example organizational process assets that are inputs to Plan Resource Management process
- Information from previous projects
- Lessons learned
Example EEFs that are inputs to the Collect Requirements process
- Organizational culture
- Organizational infrastructure
- Market conditions
Example organizational process assets that are inputs to the Collect Requirements process
- Organization’s policies and procedures
- Lessons learned
Example EEFs that are inputs to Define Scope process
Organizational culture
Example organizational process assets that are inputs to Define Scope process
Information from previous projects
Example organizational process assets that are inputs to Control Scope process
- Organization’s processes for reporting progress
- Organization’s processes for controlling changes
Example organizational process assets that are outputs of Control Scope process
Updates to lessons learned
