Managing the Project Scope

Question 1

Project Scope

Answer 1

defines everything you need to do to complete a project

Question 2

Gold Plating

Answer 2

making a component more than requirements

Question 3

Defining scope in Agile vs Traditional

Answer 3

Agile- define scope as project goes on

Traditional- define scope before work

Question 4

Scope Creep

Answer 4

scope changes without change being managed

Question 5

Causes of scope Creep

Answer 5

unexpected scope related issues
perfectionism (going beyond what is required)
pleasing stakeholders (beyond initial scope)
Misunderstandings

Question 6

Tools and Techniques for Collecting Requirements

Answer 6

Expert Judgement
Data Gathering- brainstorming, interviews, focus groups
Data Analysis- voting, mutli criteria analysis
Decision Making
Data Representation Techniques- affinity diagram, multicriteria analysis
Interpersonal and team skills
Context Diagrams
Protypes

Question 7

4 types of voting

Answer 7

Unanimity
Majority
Plurality
Autocrasty

Question 8

Nominal Group technique

Answer 8

team skill for collecting requirements
guide stakeholders in prioritizaion
let everyone have a say, anonymous, group activity but individual decision

Question 9

Buy a Feature

Answer 9

stakeholders have _____

Question 10

Requirements should be

Answer 10

clear, measurable, testable, traceable

Question 11

Requirements Trackability Matrix

Answer 11

when, why, how, requirements changed

Question 12

Tools and Techniques to define scope

Answer 12

Expert Judgement
Data Analysis
Decision Making
Interpersonal and Team skills
Product Analysis (ex: prod breakdown, system analysis)

Question 13

Project Scope

Answer 13

object, deliverables
reference documents:
Project Charter- high level
Project Management Plan > Scope Mgmt Plan

Question 14

Project scope based on

Answer 14

reference documents (project charter and scope mgmt plan)
Organizational process assets
Enterprise Environments

Question 15

Questions for defining scope

Answer 15

What must exact specifications be to meet all requirements

What must exactly be done to deliver

Question 16

Project Scope statment

Answer 16

4 components
Description- all attributes to meet requirements (ex: avail 98% of time)
Deliverables- what stakeholders can expect to receive (ex: reports, end product, approval)
Exclusions- what isn’t included (ex: video doesn’t include audio)
Acceptance Criteria- standards that are agreed to (verify scope, confirm completion and acceptance)

Question 17

Work Breakdown Structure (WBS)

Answer 17

breaks work into manageable units
Benefits:
1 helps define responsibilities
2 better control of project (monitor and control budget and facilitates accurate progress reports)
3 helps with scheduling
4 facilitates budget creation

Question 18

Work Breakdown Structure format

Answer 18

multiple layers- usually 4-6 levels
top- project name
2nd- broadest definitions, can be phase based or deliverable based (ex: planning, administration,
tasks
subtasks
work packages

Question 19

100% rule (WBS)

Answer 19

each level of WBS must add up to 100% of level above

Question 20

Tools and Techniques to create Work Breakdown Structure

Answer 20

Expert Judgement

Decomposition

Question 21

Pros and Cons of Decomposition

Answer 21

pro-
resources, costs, schedule estimates are easier

con-
over decomposition- goes too small, waste of time and overwhelming

Question 22

Activities in Decomposition

Answer 22

1- Id deliverables- from scope statement
2- Structure and organize WBS- in scope mgmt
3- Decompose deliverable
4- Assign identification codes
5- Verify WBS- look at templates, use similar

Question 23

8/80 rule

Answer 23

when decomposing requirements, aim to be between 8-80 hours for each deliverable

Question 24

WBS Verfication

Answer 24

Expert judgement

• clear and complete
• 100% of work is represented at next level
• reasonable duration
• Id is logical
• Integration is included
• Project Management included (on second level)
• Contract work included (the deliverable, not org)
• matches business norms

Question 25

WBS Finalization

Answer 25

ID components that need monitoring and establish control points at which you will use performance analysis to compare performance vs baseline

Question 26

Control points

Answer 26

during finalization of WBS, they are added
at each control point- check performance
must be apporpriate level

Question 27

WBS Dictionary

Answer 27

details that don’t fit in WBS
name and WBS component
position in WBS, who is responsible, requirement #, scope description (instructions to complete package), who prepared the form, date of sign off, schedule and cost estimate, milestones

Question 28

Validation of Scope

Answer 28

confirm deliverables are accepted

• id the deliverables, are they meeting requirements?
• validate each deliverable internally before to stakeholders
• project isn’t complete until stakeholder accepts

Question 29

Validation vs Control Quality

Answer 29

validation- all requirements are included and accepted
purpose- product meets requirement
who- PM and customer
review against- requirement documentation
vs
quality- deliverables are correct and meet quality requirements
purpose- id and eliminate poor quality
who- QA dept, PM and team
review against- predefined standards

Question 30

Types of Scope Change

Answer 30

Managed- via change request, manage scope creep, only beneficial changes
Unmanaged change- not planned, scope creep or variance, negative impact to schedule/budget, halt until corrected

Question 31

Variance Analysis

Answer 31

used in controlling scope, type of dat analysis

• id variance
• id cause