Scope Management

Question 1

Inverted Triangle Model

Answer 1

Time and cost is fixed, scope is varied

Question 2

Triple Constraints Triangle Model

Answer 2

Scope is fixed, time and cost are varied

Question 3

Grooming the Backlog

Answer 3

Product owner owns the backlog items, backlog refinement is the prioritization of backlog items

Question 4

Scrum Artifact

Answer 4

Product backlog is the source for all product requirements, product owner sorts and prioritizes backlog items, development team works on most important items based on prioritized items in the product backlog

Question 5

Collecting Project Requirements

Answer 5

Process of determining, documenting, and managing requirements

Question 6

Project Requirements

Answer 6

Help define product and project scope

Question 7

Benchmarking

Answer 7

Comparing two or more system, businesses, approaches. Set an external basis for performance, and comparing organizations for requirements.

Question 8

Multicriteria Analysis

Answer 8

Systematic approach of determining, ranking, and eliminating project criteria. Performance metrics, risks, requirements

Question 9

Affinity Diagram

Answer 9

Creativity technique used to identify solutions - groups ideas into clusters, each of which can be broken down again to analyze each subset

Question 10

Mind Mapping

Answer 10

Brainstorm ideas, consolidate ideas, helps generate new ideas

Question 11

Nominal Group Technique

Answer 11

1. generate ideas and then vote on and rank ideas based on usefulness 2. each participant brainstorms the problem or opportunity with their ideas 3. The facilitator will add all ideas each person has created to a white board 4. ideas are discussed for clarify and understanding 5. privately vote on each idea from 1 to a high score of 5. rounds of voting and discussion take place to find a consensus on highest-scoring ideas

Question 12

Facilitated Workshop

Answer 12

Joint application design - software development; SMEs and dev team meet to gather requirements

Question 13

Agile Requirements Gathering

Answer 13

User stories define:
Role (who) - who benefits from the feature
Goal (what) - what the stakeholder aims to accomplish
Motivation (why) - benefit to the stakeholder

Question 14

Context Diagram

Answer 14

Takes a requirement and puts it into context to how people interact with the item/product

Question 15

Business Requirements

Answer 15

Higher level needs of the organization

Question 16

Stakeholder Requirements

Answer 16

Needs of a stakeholder or stakeholder group

Question 17

Solution Requirements

Answer 17

Features, functions, and characteristics of the product, service

Question 18

Functional Requirements

Answer 18

Describe the behaviors of a product

Question 19

Nonfunctional Requirements

Answer 19

Describe the environmental conditions or qualities

Question 20

Transition Requirements

Answer 20

From the current state to the future state (operational)

Question 21

Project Requirements

Answer 21

Actions, processes, or other conditions

Question 22

Quality Requirements

Answer 22

Validate the successful completion of a project deliverable or fulfillment

Question 23

Requirements Traceability Matrix

Answer 23

Based on requirements collection. A table that allows you to trace requirements across the project from entry, executing, into operations to track several characteristics

Question 24

Defining the Project Scope Statement

Answer 24

Developing a detailed description of the project and product, describes the product, service, or result and establishes boundaries and acceptance criteria

Question 25

Scope Baseline

Answer 25

Project scope statement, Project WBS, Project WBS dictionary

Question 26

Work Breakdown Structure

Answer 26

Decomposition of project scope and subdivides the project work, deliverables oriented, visualizes the project, defines what’s in scope, serves as a deterrent to change

Question 27

WBS Dictionary

Answer 27

Describes each item that we’re creating. Taking each deliverable and defining it.

Question 28

Four Inputs for WBS Creation

Answer 28

Project Management Plan, Project documents, Enterprise environmental factors, Organizational process assets

Question 29

Control accounts

Answer 29

Markers in the WBS that serve as a point of reconciliation for the project’s costs, schedule, and scope achievement in the project.

Question 30

The WBS Dictionary should provide these things for each work package:

Answer 30

1. A code of account identifier
2. A description of what the element is
3. Who is responsible for the WBS element
4. Associated activities for the WBS element
5. Required resources (such as people, equipment, and materials)
6. The cost for the WBS element
7. Quality and acceptance criteria
8. Technical information when needed
9. Vendors and associated contract information

Question 31

Validate Scope

Answer 31

Inspection driven process - customer inspects project work to ensure phase and project completion. Reviews, audits, or walkthrough of what’s been created to get customer to accept the project as completed

Question 32

Controlling Project Scope

Answer 32

Monitoring the status of the project and product scope, maintaining the scope baseline integrity to keep the project in scope

Question 33

Variance Analysis

Answer 33

What was delivered vs what was expected, magnitude of variation, corrective or preventative action

Question 34

Trend Analysis

Answer 34

Predict what is going to happen based on past experiences, project performance over time, are we improving or deteriorating

Question 35

Provides details about how the project scope may be changed

Answer 35

Scope Management Plan