Chapter 5. Scope Management Flashcards
1
Q
What does scope refer to?
A
It may refer to the scope of the entire project or the scope of a product. it is everything that must be completed in order to meet product requirements, while project scope include everything in the entire project.
2
Q
What are the processes associated with Scope Management?
A
Define Scope Collect Requirements Plan Scope Management Create WBS Control Scope Validate Scope
3
Q
What is the output of Define Scope?
A
Project Scope Statement
4
Q
What is the output of Plan Scope Management?
A
Scope Management Plan
Requirements Management Plan
5
Q
What is the output of Collect Requirements?
A
Requirements Documentation
Requirements Traceability Matrix
6
Q
What is the output of Create WBS?
A
Scope Baseline
7
Q
What is the output of Control Scope?
A
Work Performance Information
8
Q
What is the output of Validate Scope?
A
Accepted Deliverables
9
Q
Wha tis the philosophy of Scope Management?
A
Project Mananger should always be in control of the scope by thoroughly defining it and carefully managing the process.
Changes to the scope should be handled in a structured and controlled way.
10
Q
Good scope management ensures what?
A
Scope is well defined and clearly communicated, so that the project is carefully managed to limit unnecessary changes. Scope is referring to the work needed to successfully complete the project and ONLY that work.
11
Q
Scope changes must be….
A
Detected, evaluated and documented
12
Q
What are the overall goals of scope management?
A
Define the need. Set stakeholder expectations. Deliver to the expectations. Manage changes. Minimize surprises.
13
Q
What is “gold plating?”
A
A company’s attempt to exceed customer expectation by delivering more than was agreed upon.
14
Q
What is the problem with “gold plating?”
A
It increases risk and uncertainty, and may add potential problems into the project. Ideally, you want to avoid gold plating.
15
Q
What are the knowledge areas associated with scope planning?
A
- Planning the overall scope-related efforts
- Gathering the requirements for the product and project
- Defining and documenting the deliverables that are a part of the product and project (the scope
- Creating the work breakdown structure (WBS) and baselining the scope
- Checking the work being done against the scope to ensure that it is complete
- Ensuring that all of what is “in scope” and only what is “in scope” is completed and that changes are properly managed.
16
Q
What are the processes of scope management that fall under the Planning Process Group?
A
Plan Scope Management
Collect Requirements
Define Scope
Create Work Breakdown Structure (WBS)
17
Q
What are the processes of scope management that fall under the Monitoring and Controlling Process Group?
A
Validate Scope, Control Scope
18
Q
Which Process Groups are not associated with Scope Management?
A
Initiating, Executing and Closing
19
Q
What are the outputs associated with the 6 processes of Scope Management?
A
Plan Scope Management - Scope Management Plan, Requirements Management Plan
Collect Requirements - Requirements Documentation, Requirements Traceability Matrix
Define Scope - Project Scope Statement
Create Work Breakdown Structure (WBS) - Scope Baseline
Validate Scope - Accepted Deliverables
Control Scope - Work Performance Information
20
Q
What else ties into Plan Scope Management?
A
Schedule, budget, quality specifications, risk factors and resource planning.
21
Q
What is the Scope Management Plan part of?
A
The Project Management Plan. However, the Project Management Plan is also an input into Plan Scope Management.
22
Q
What are the Inputs of Plan Scope Management?
A
Project Charter
Project Management Plan usually unfinished at this point
Enterprise Environmental Factors
Organizational Process Assets
23
Q
What are the tools for Plan Scope Management?
A
Expert Judgement
Data Analysis
Meetings
24
Q
What are outputs of Plan Scope Management?
A
Scope Managment Plan
Requirements Management Plan
25
What is a Requirements Managment Plan?
It defines what activities the team will perform in order to gather and manage the project requirements (plan for how requirements will be managed but does not contain the requirements themselves). Shows how requirements will be gather, how decisions will be made, how changes will be handled and how the requirements will be documented.
26
Why is collect requirements so important?
It allows the project manager to set and manage stakeholder expectations.
27
Collect Requirements comes after what?
Develop Project Charter > project charter > Identify Stakeholders > stake holder register > Collect Requirements
28
What are the inputs for Collect Requirements?
```
Scope Management Plan
Requirements Management Plan
Stakeholder Engagement Plan
Project Documents (such as Assumption Log, Lessons Learned Register, Stakeholder Register)
Business Document (such as the Business Case)
Agreements
Enterprise Environmental Factors
Organizational Process Assets
```
29
What does the Stakeholder Engagement Plan do?
Informs how deeply the stakeholders should be involved in the requirements process and that should be carried out.
30
What are the tools used for Collect Requirements?
```
Expert Judgement
Brainstorming
Interviews
Focus Groups
Questionnaires and Surveys
Benchmarking
Data Analysis
Decision Making (may include voting and multicriteria decision analysis)
Data Representation (may include Affinity Diagrams and Mind Mapping)
Interpersonal and Team Skills (may include Nominal Group Technique, Observation and Conversation, and Facilitation)
Context Diagram
Prototypes
```
31
What is benchmarking used for?
To look outside of the project to understand best practices and gain inspiration. Best to look at other organizations and projects that have something in common with your project.
32
What are the different types of voting that can be used?
Unanimity, Majority, Consensus, Plurality, and Autocratic Decision Making
33
What is Multicriteria Decision Analysis?
A technique that uses a weighted matrix to assign values to each criterion and then rate them accordingly.
34
What are Affinity Diagrams?
Takes ideas from a brainstorming session and organizes them into logical groups or categories.
35
What is Mind Mapping?
A technique of diagramming ideas and creating meaningful associations in a graphical format.
36
What is a nominal group technique?
Group brainstorming ideas that get voted on, then sorted by priority.
37
What is job shadowing?
Observation of a worker, who is studied as he performs his job.
38
What is facilitation in terms of a tool?
Workshops to colocate all key stakeholders together and to elaborate requirements. Needs to be led by a skilled facilitator. Examples of Faciliated Workshops include Joint Application Development, Quality Function Deployment and User Stories.
39
What is a context diagram?
Generic term for a use case diagram, shows systems and "actors" that interact with each system.
40
What are prototypes?
Interactive models of a product.
41
Beyond models, what is another way of prototyping?
Storyboarding the flow of a product.
42
What are the outputs of Collect Requirements?
Required Documentation
| Requirements Traceability Matrix
43
What should Required Documentation include?
Root business problem being solved
Source of the requirement
Way each requirement addresses the problem
How the business processes interact with the requirements
Associated measurements for each requirement
business, legal, and ethical compliance
Contraints and assumptions
Anticipated impact of the requirement on others
44
If a requirement is important enough to be documented, it is important enough to document what else?
The source
45
What should a Requirements Traceability Matrix include?
```
Req ID
Date
Description
Business Need
WBS Deliverables
Origin of Request (Source)
User Acceptance Test Case
```
46
Define Scope is what?
The process where the project's requirements are more thoroughly understood and documented.
47
When is Define Scope performed?
Develop Project Charter = Project Charter > Identify Stakeholders = Stakeholder Register > Collect Requirements = Requirements Documentation > Define Scope
(Develop Project Charter, Identify Stakeholders and Collect Requirements must be completed before it is possible to perform Define Scope).
48
What are the inputs for Define Scope?
```
Project Charter
Project Management Plan
Assumption Log
Requirements Documentation
Risk Register
Enterprise Environmental Factors
Organizational Process Assets
```
49
What tools are used for Define Scope?
```
Expert Judgement
Data Analysis
Decision Making
Interpersonal and Team Skills
Product Analysis
```
50
Tools used in Product Analysis include
```
Product Breakdown
Requirements Analysis
Systems Analysis
Systems Engineering
Value Analysis
Value Engineering
```
51
What are Outputs of Define Scope?
```
Project Scope Statement
Product Scope Description
Deliverables
Acceptance Criteria
Project Exclusions
Project Documents Updates
```
52
What is a Project Scope Statement?
Document used to level-set among the project's stakeholders.
53
What are Project Exclusions?
What is out of scope for the project.
54
What is the main product and output for Create WBS?
The WBS is the main product but the output is the Scope Baseline.
55
When is Create WBS performed?
Develop Project Charter > Identify Stakeholders > Collect Requirements > Define Scope > Create WBS (comes after the Project Work Statement has been written)
56
What are the inputs to Create WBS?
```
Project Management Plan
Project Documents
- Project Scope Statement
- Requirements Document
Enterprise Environmental Factors
Organizational Process Assets
```
57
What is the most important component of the project management plan to Create WBS & why?
The Scope Management Plan, which describes the approach the team will use on the project and how it will be carried out.
58
What does the Project Scope Statement do?
Describe the scope of the project. It is the primary starting point from which to build the WBS.
59
In the case of Create WBS, what are the most common assets?
Methodologies that spell out how to create the work breakdown structure, software tools to create the graphical chart, WBS templates, and completed WBS Examples from previously performed projects.
60
What are the tools used for Create WBS?
Decomposition - breaking down the project deliverables in to progressively smaller components. Large pieces are progressively broken down into smaller and smaller pieces.
61
What are the 3 rules for determining how far to decompose work?
1. Are your work packages small enough to be estimated for time and cost?
2. Are the project manager and the project team satisifeid that the current level of detail provides enough information to proceed with subsequent project activities?
3. Is each work package small enough to be able to be assigned to a single person or group that can be responsible for the results?
62
In Agile projects, how does decomposition work?
Using a rolling wave technique, in which all of the decomposition does not occur at once. Parts of the WBS are decomposed and then work carried out in the form of product development. Then more of the WBS is decomposied and then that work is carried out. So, that these activities repeat like waves.
63
What are the outputs of Create WBS?
1. Scope Baseline
2. WBS - The Work Breakdown Structure, a graphical, hierarchical chart, logically organized from top to botton.
Note: The WBS is always based on project deliverables, rather than tasks needed to create those deliverables.
3. Work Package
4. Planning Package
5. Control Account
6. WBS Dictionary
7. Project Document Updates - should document any changes in understanding.
64
A node may be considered a work package when it meets what criteria?
- The work package cannot be easily decomposed any further.
- The work package is small enough to be estimated for time (effort).
- The work package is small enough to be estimated for cost.
and
- The work package may be assigned to a single person or group for responsibility.
65
If an item is not in the WBS what should happen?
It does not get delivered with the project.
66
Who creates the WBS?
The project team AND the project manager.
67
What integration tool allows you to see where the individual pieces of work fit into a project as a whole?
The WBS (Work Breakdown Structure)
68
What is a work package?
The lowest level of the WBS (Work Breakdown Structure)
69
What is a planning package?
Node on the WBS (Work Breakdown Structure) that are larger than work packages but that cannot be broken down into work packages at this time, usually bc not enough information is known yet.
70
What is a control account?
A node on the WBS where the scope, time and cost are measured, used to measure earned value.
71
A control account is also known as what?
A cost account
72
What is a WBS dictionary?
A document that details the contents of the WBS, providing detailed information about the nodes on a WBS. Captures additional attributes of each work package in a different document and does not have the graphical constraints of a WBS. (see p. 188 for Sample WBS Dictionary Entry)
73
What is the Monitoring & Controlling Validate Scope process within Scope Management?
Comparing outputs with the plan, identifying any variances and taking corrective action, if required.
74
Validate Scope is primarily concerned with what?
Completeness and acceptance of the product.
75
If a project is canceled, what does Validate Scope accomplish?
It documents where the project was in relation to the scope at the point when the project ended.
76
Who accepts a product?
The Project Manager, the customer, the sponsor and sometimes the functional managers and key stakeholders.
77
When should Validate Scope happen?
After at least some/part of a product has been delivered, although it may be performed multiple times throughout the life of the project. Always performed at least once.
78
What are inputs to Validate Scope in Scope Management?
Project Management Plan
Project Documents
Verified Deliverables
Work Performance Data
79
What does Work Performance Data do?
Tell how the deliverables were created, so that the path can be evaluated and improved upon for future projects.
80
What are the tools used in Validate Scope in Scope Management?
Inspection - a point by point review of scope vs associated deliverable
Decision-Making
81
What are the outputs for Validate Scope in Scope Management?
Accepted Deliverables
Work Performance Information
Change Requests
Project Document Updates
82
What is the Control Scope process in Scope Management?
Maintaining control of the project by preventing scope change requests from overwhelming the project, and also making certain that scope change requests are properly handled. Involves always keeping scope baseline current.
83
What is one of the more challenging aspects of Control Scope?
Resolving Disputes
*Customer's interests should always be weighed heavily and whenever possible, disputes should be resolved in favor of the customer.
84
When is Control Scope performed?
After Scope Baseline is established.
85
What are the inputs to Control Scope?
Project Management Plan - contains scope management plan and scope baseline
Project Documents
Work Performance Data
Organizatonal Process Assets
86
What are the tools used in Control Scope?
Data Analysis - specifically variance and trend analysis
87
What are the outputs of Control Scope?
Work Performance Information (WPI)
Change Requests
Project Management Plan Updates
Project Documents Updates
88
What Agile practice does decomposition in Create WBS correspond to?
Disaggregation, where epics or large user stories are broken down into smaller, component user stories.
See p. 197 for more specifics.
89
Regarding a work breakdown structure, do activities have to be arranged in the sequence they will be performed in?
No. False.
90
Mark has taken over a project that is beginning the construction phase of the product; however; he discovers that no work breakdown structure has been created. What should Mark do?
He should stop construction until the work breakdown structure has been created.
91
A project has completed execution, and now it is time for the product of the project to be accepted. Who formally accepts the product?
The sponsor, the key stakeholders and the customer.
92
The project scope statement should contain:
A detailed description of the scope.
93
Are requirements documentation part of the scope baseline?
No.
94
You have taken over as project manager for a data warehousing project that is completing the design phase; however, change requests that affect the requirements are still pouring in from many sources, including your boss. What would be beneficial to this situation?
A well-defined requirements management plan, because it contains a plan for how changes will be handled. If too many changes are flowing in, it is likely that the requirements management plan was not well defined.
95
A project team has a dedicated scoping phase for their project where all subject matter experts are meeting together with a trained facilitator. They have interviewed each person in the room to gather ideas for functionality and are now voting on them to put them in order of priority. This list will be used to feed requirements to the project team. The group's activities are an example of:
The Nominal Group Technique -
Starts by gathering a large field of candidate items (in this case scope items) and voting to sort them from highest to lowest in order of priority.
96
Your agile team has defined what "Done" means on the project. When is "Done" applied and by whom?
By the team during test-driven developement, and by the users during product demonstrations.
97
Concerning Functionality that is over and above the documented scope....
The final product should include all the functionality and only the functionality documented in the scope baseline.
