Scope Flashcards

1
Q

This technique helps elicit opinions and requirements for the product or an aspect of the project from stakeholders and subject matter experts. The conversation is usually directed by a moderator.

A

Focus Groups

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the (5) inputs of the Collect Requirements process?

A
  1. Project charter
  2. Assumption log
  3. Stakeholder register
  4. Agreements
  5. Organizational process assets (OPAs)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

This technique focuses on measuring an organization’s performance against that of other organizations in the same industry.

A

Benchmarking

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

__________ __________ is another way to say “requirements that relate to the product, service, or result of the project.” It can also be defined as the product deliverables with their associated features and functions.

A

Product Scope

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the items at the lowest level of the WBS?

A

Work Packages

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What (6) steps does the scope management process include?

A
  1. Develop a plan to plan, validate, and control scope and requirements on the project.
  2. Determine requirements, make sure they support the project’s business case as described in the project charter.
  3. Sort and balance the needs of stakeholders to determine scope.
  4. Create a WBS to break scope down to smaller and define each piece in the WBS dictionary.
  5. Obtain validation that the completed scope of work is acceptable to the customer or sponsor.
  6. Measure scope performance and adjust as needed.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

This is a visual, organizational tool showing all of the scope on a project, broken down into manageable deliverables as work packages. It helps ensure that no deliverables are missed and it is a required artifact for all projects in a plan-driven predictive environment.

A

Work Breakdown Structure (WBS)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

__________ __________ is a tool to define scope that generally means asking questions about a product and forming answers to describe the use, characteristics, and other relevant aspects of what is going to be manufactured.

A

Product Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

A __________ is a short, fixed period in which a defined set of activities or work is undertaken. This techniques allows agile teams to adjust their scope to achieve the highest-priority, best-quality product within a fixed cost and timeframe.

A

Timebox

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

The purpose of this technique is not so much to get individuals to share their thoughts on a topic as it is to encourage participants to build on each other’s ideas.

A

Brainstorming

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

This technique is usually done during the same meeting as brainstorming. It tends to be more structured than other techniques, and follows these four steps: a question or issue is posed, all meeting participants write down and then share their ideas, the group discusses what’s been shared, and then ideas are ranked based on which ideas are the most useful.

A

Nominal Group Technique

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What (3) items make up the Scope Baseline?

A
  1. WBS
  2. WBS Dictionary
  3. Project scope statement
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What plan answers the following questions: Once I have as many requirements as I can gather, what will I do to analyze, prioritize, manage, and track changes? What should I include in the requirements traceability matrix?

A

Requirements Management Plan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

This tool helps link requirements to the objectives and/or other requirements to ensure the strategic goals are accomplished. It is used throughout the project in analyzing proposed changes to project or product scope.

A

Requirements Traceability Matrix

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

This document provides a description of the work to be done for each WBS work package, and it lists the acceptance criteria for each deliverable, which ensure the resulting work matches what is needed.

A

WBS Dictionary

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

This tool is a single, visible master list of all the functional and nonfunctional work identified for the project. In other words, it is a list of work that needs to be done, and items are removed from the list as they are completed. It is essentially a list of the expected work to deliver the product.

A

Product Backlog

17
Q

This is a way to learn about business processes and to get a feel for the work environment of stakeholders. This technique generally involves job shadowing and, in some cases, participating in the work to help identify requirements.

A

Observation

18
Q

Another way to rank ideas is through this technique. Stakeholders quantify requirements using a decision matrix based on factors such as expected risk levels, time estimates, and cost and benefit estimates.

A

Multicriteria Decision Analysis

19
Q

This communication tool is a visual depiction of the product releases and the main components that will be included in each release of an agile project. It provides the stakeholders with a quick view of the primary release points and intended functionality that will be delivered.

A

Product Roadmap

20
Q

In this technique, the ideas generated from any other requirements-gathering techniques are grouped by similarities. Each group of requirements is then given a title. This sorting makes it easier to see addtional areas of scope that have not been idetified.

A

Affinity Diagram

21
Q

What is a tool that allows you to collect and analyze work performance data regarding costs, schedule, and scope? It may include one or more planning packages. Each work package in the WBS is assigned to only one of these.

A

Control Account

22
Q

This technique utilizes a diagram of ideas or notes to help generate, classify, or record information. It branches out of a central core word or words.

A

Mind Maps

23
Q

What (4) items does the Scope Management Plan describe how to do?

A
  1. Achieve the overall project scope
  2. Create the WBS or product backlog and stories
  3. Manage and control scope to the project management plan
  4. Obtain acceptance of deliverables
24
Q

This type of diagram is frequently used to define and model scope. It shows the boundaries of the product scope by highlighting the product and its interfaces with people, processes, or systems.

A

Context Diagram

25
Q

What are the (6) processes of Scope Management?

A
  1. Plan Scope Management - Planning
  2. Collect Requirements - Planning
  3. Define Scope - Planning
  4. Create WBS - Planning
  5. Validate Scope - M&C
  6. Control Scope - M&C
26
Q

The work the project team will do to deliver the product of the project; it encompasses the product scope.

A

Project Scope

27
Q

A model of the proposed product that is presented for feedback. It may be updated multiple times to incorporate stakeholders’ feedback until the requirements have been solidified for the product,

A

Prototype

28
Q

This technique brings together stakeholders with different perspectives to talk about the product and define requirements. This technique uses a consensus approach, which achieves general agreement about a decision.

A

Facilitation

29
Q

The description of the project scope, major deliverables, assumptions, and constraints.

A

Project Scope Statement

30
Q

Includes items from the product packlog that can conceivably be completed within the time period based on the team’s capacity.

A

Sprint or Iteration Backlog

31
Q

Who is responsible for reprioritizing the backlog as stories or requirements change?

A

Product Owner

32
Q

A team’s checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use.

A

Definition of Done

33
Q

A team’s checklist for a user-centric requirement that has all the information the team needs to be able to begin working on it.

A

Definition of Ready

34
Q

At or near the conclusion of a timeboxed iteration, the project team shares and demonstrates all the work produced during the iteration with the business and other stakeholders.

A

Iteration/Sprint Review (Demo)