Project Scope Management

Question 1

Predictive

Answer 1

Scoped defined at beginning
Change resistant

Question 2

Adaptive

Answer 2

Project scope developed throughout iterations
Expect changes

Question 3

Product Scope

Answer 3

Features or functions
Does not tell you what the project is about, just tells you what it can do
Characteristics of what customers expect, their deliverables.
Productive backlog in adaptive

Question 4

Product Backlog

Answer 4

Big list of all requirements
Prioritized

Question 5

Scope

Answer 5

What the project will actually accomplish
Includes ONLY the work required

Question 6

Project Scope

Answer 6

Work needed to deliver a product, service, or result.
Actually tells you what the project is about

Question 7

Plan Scope Management PROCESS

Answer 7

In Planning Process Group

Main Output Creating Scope Management Plan and Requirement Management Plans

PM documents next steps needed to do the next 5 processes in this area

Project Management plan is an input

Question 8

Collect Requirements PROCESS

Answer 8

In Planning Process Group

Defining and documenting stakeholders needs to meet project objectives

Main Output= Requirements Documentation and Requirement Traceability Matrix

Question 9

Define Scope PROCESS

Answer 9

In Planning Process group

Main output= Create project scope statement

Scope is iterative- May take time to determine actual scope

In a Traditional project, scope is stored in project scope statements

In a Agile Project, scope is stored in product backlog

Question 10

Create Work Breakdown Structure PROCESS

Answer 10

In Planning Process Group

Breaking down deliverables into smaller more manageable components–

Main output is scope baseline

WBS is hierarchical , top level is general, lower level is detailed

Control accounts are broken down into work packages

Question 11

Validate Scope PROCESS

Answer 11

In Monitoring and Controlling Process group

Main Output= Accepted deliverables and Work Performance Information

Project deliverables are formally inspected and accepted by the customer or sponsor

Done at the end of a project

Question 12

Control Scope PROCESS

Answer 12

In Monitoring and Controlling Process group

Main output= Change Request and Work Performance Information

Goal is to ensure project stays on scope as it is executed

Make sure the work the project team is doing is actually in the scope
done on a daily basis

Question 13

Product Road Map

Answer 13

Agile
High level document that outlines what would be expected of the actual project
Outlines all of the releases

Question 14

Benchmarking

Answer 14

Looking at industry best practices for how fast a website should load

Question 15

Idea Mapping

Answer 15

Way to represent data
Ideas are drawn instead of written

Question 16

Joint Application Development JAD

Answer 16

Subject matter experts and developers meet to improve the software development process

Question 17

Prototypes

Answer 17

Working models of a product that stakeholders can interact with.
Agile uses prototypes

Question 18

Storyboarding

Answer 18

Prototyping technique used on agile projects
it is a series of images that are used to show a mockup of what the program would look like once a user is using it.

Question 19

Facilitation

Answer 19

Bring together stakeholders to gather requirements
EX workshop

Question 20

Obeservation

Answer 20

Viewing stakeholders in their work enviroment

Question 21

User Stories

Answer 21

As a <role/user type>, I want <goal> so that <motivation/reason></goal>

Question 22

Requirements Traceability Matrix

Answer 22

Table created to link requirements back to their origin.

Question 23

Project Scope Statement

Answer 23

Includes:
Description of scope
Acceptance Criteria
Exclusions
Constraints
Assumptions
Explains project deliverables and work required to complete the deliverables

Question 24

Risk Register

Answer 24

Shows risks that can impact the scope

Question 25

Decomposition

Answer 25

Take project deliverables from scope statement and divide them into smaller parts, known as work packages (Lowest level on WBS used to estimate time and cost)

Question 26

Scope Baseline

Answer 26

Made up of three components
-Project scope statement
-WBS
-WBS Dictionary

Question 27

WBS Dictionary

Answer 27

document that has more details about each work package

Question 28

Epics

Answer 28

How work is decomposed on an agile project
large initiatives to deliver new products or solutions to customers.
Epics are decomposed into features
Features are decomposed into stories
and task are the the decomposition of user stories

Question 29

Control Quality

Answer 29

Process where deliverable is inspected to see if it meets the quality requirements
Do this before you take to a customer or sponsor for formal acceptance

Question 30

Variance Analysis

Answer 30

Determines if there is a variance between the planned work (PM Plan) and the actual work (Work performance data)

Question 31

Work Performance Information

Answer 31

States if project is in scope or not

Question 32

Completion of Project scope is Measured against?

Answer 32

Project Management Plan
Project Scope Statement
The WBS
WBS Dictionary

Question 33

Code of Accounts

Answer 33

Formal name for numbering system found in WBS
it allows the following:
-Link the work packages to specific account codes used to track project costs
-Helps project manager identify level at which work package is found