Scope Mgmt

Question 1

Scope mgmt

Answer 1

Help understand requirements, define, breakdown, and control the scope of the project and verify product was completed correctly

Question 2

Product scope

Answer 2

Everything that must be completed in order to meet product requirements

Question 3

Project scope

Answer 3

Everything in the entire project plan

Ex: lessons learned

Question 4

Scope mgmt philosophy

Answer 4

1) the project mgr should always be in control of the scope by thoroughly defining it and managing the processes
2) changes to the scope should be handled in a controlled and structured way

Question 5

Scope mgmt goals

Answer 5

Define the need, set stakeholder expectations, deliver expectations, manage changes, minimize surprises so product will gain approval

Question 6

Scope management processes

Answer 6

Initiating - none
Planning - plan scope mgmt, collect requirements, define scope, create wbs
Executing - none
Monitoring and controlling- validate scope, control scope
Closing - none

Question 7

Plan scope mgmt output

Answer 7

Scope mgmt plan, requirements mgmt plan

Question 8

Collect requirements output

Answer 8

Requirements documentation, requirements traceability matrix

Question 9

Define scope output

Answer 9

Project scope statement

Question 10

Create wbs output

Answer 10

Scope baseline

Question 11

Validate scope output

Answer 11

Accepted deliverables

Question 12

Control scope output

Answer 12

Scope change requests, work performance information

Question 13

Plan scope mgmt

Answer 13

Looks at the five other processes and plans the overall approach

Schedule, budget, quality, risk factors and resource planning all tie back to it

Question 14

Scope mgmt plan

Answer 14

Describes how scope documents will be prepared and his five remaining processes will be carried out

Question 15

Requirements mgmt plan

Answer 15

Defines what activities the team will perform to gather and manage project requirements

Not a list of actual work requirements, just how they will be managed

Question 16

Collect requirements

Answer 16

What is needed to satisfy stakeholders and documenting it

Product and project scope

Needs project charter and identify stakeholders complete

Question 17

Collect requirements tools - data gathering

Answer 17

Brainstorming, interviews, focus groups, questionnaires, benchmarking

Question 18

Collect requirements- decision making

Answer 18

Voting, multicriteria decision analysis (C&e matrix)

Question 19

Affinity diagram

Answer 19

Takes ideas from brainstorming and organizes into logical groups

Question 20

Mind mapping

Answer 20

Diagraming India’s into a graphical format

Question 21

Collect requirements- data representation

Answer 21

Mind mapping, affinity diagrams

Question 22

Nominal group

Answer 22

Ideas are brainstormed and then voted on and sorted by priority

Question 23

Observation and conversation

Answer 23

Job shadowing

Question 24

Facilitation

Answer 24

Workshop, get everyone together and gather req

Question 25

Collect requirements- interpersonal team skills

Answer 25

Nominal group, observation and conversation, facilitating

Question 26

Context diagram

Answer 26

Use case

Question 27

Requirements documentation

Answer 27

Root business problem, source, way requirements addresses problem, business process interaction, measurements, compliance, constraints/assumptions, impact on other requirements

Question 28

Requirements traceability matrix

Answer 28

Identifies source of requirement and can include status and owner

Question 29

Define scope

Answer 29

Where project req are more thoroughly understood and documented

Occurs after collect req

Question 30

Product analysis

Answer 30

Intent on improving teams understanding of a product and thus requirements

Product breakdown, req analysis, sys analysis, sys eng, value analysis, value eng

Question 31

Project scope statement

Answer 31

Document used to level set stakeholders

Goals, product description, req, constraints/assumptions, identified risks

Product scope statement, deliverables, acceptance criteria, project exclusions

Question 32

Create wbs

Answer 32

Main output is actually scope baseline

Question 33

Decomposition

Answer 33

Process of breaking down project deliverables into progressively smaller units

Small enough to associate time and cost to one person

Question 34

Scope baseline

Answer 34

Combo of project scope statement, wbs, wbs dictionary, work packages and planning packages

Question 35

WBS

Answer 35

Work breakdown structure

Detailed, top down, graphical/hierarchical chart

Name, number, cost, time

Question 36

Work package

Answer 36

Lowest level of wbs

Question 37

Planning package

Answer 37

Not enough info to create wbs, too large

Question 38

Control account

Answer 38

Cost account - scope, time, cost measured

Question 39

Wbs dictionary

Answer 39

Details of wbs work packages

Name, number, cost, time, description, due dates, who

Question 40

Validate scope

Answer 40

Ensuring hat product/service/result matches the documented scope

Inspecting verified deliverables into outputs of accepted deliverables

Concerned with completeness

Question 41

Validate scope tool

Answer 41

Inspection

Question 42

Control scope

Answer 42

Maintaining control of project by preventing scope changes from overwhelming the project and properly handling them

Customer isn’t always right but is the most important stakeholder - disputes should favor them

Performed once baseline is created