5 Flashcards

1
Q

It includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Managing it, is primarily concerned with defining and controlling what is and is not included in the project.

A

Project Scope Management

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

• The Project Scope Management processes are:

A
o	Plan Scope Management
o	Collect Requirements
o	Define Scope
o	Create WBS
o	Validate Scope
o	Control Scope
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

The process of creating a scope management plan that documents how the project and product scope will be defined, validated, and controlled.

A

Plan Scope Management

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

The process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.

A

Collect Requirements

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

The process of developing a detailed description of the project and product.

A

Define Scope

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

The process of subdividing project deliverables and project work into smaller, more manageable components.

A

Create WBS

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

The process of formalizing acceptance of the completed project deliverables.

A

Validate Scope

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

The process of monitoring the status of the project and product scope and managing changes to the scope baseline.

A

Control Scope

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

The features and functions that characterize a product, service, or result.

A

Product scope

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

The work performed to deliver a product, service, or result with the specified features and functions. It´s sometimes viewed as including product scope.

A

Project scope

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

In this life cycle, the project deliverables are defined at the beginning of the project and any changes to the scope are progressively managed.

A

Predictive life cycle

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

In this life cycle, the deliverables are developed over multiple iterations where a detailed scope is defined and approved for each iteration when it begins.

A

adaptive or agile life cycle

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

The overall scope of an adaptive project will be decomposed into a set of requirements and work to be performed, sometimes referred to as:

A

Product backlog

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

This term is defined as a condition or capability that is required to be present in a product, service, or result to satisfy an agreement or other formally imposed specification

A

Requirement

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

The key benefit of this process is that it provides guidance and direction on how scope will be managed throughout the project.

A

Plan Scope Management

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

The components of a scope management plan include: (al menos tener idea)

A

 Process for preparing a project scope statement;
 Process that enables the creation of the WBS from the detailed project scope statement;
 Process that establishes how the scope baseline will be approved and maintained; and
 Process that specifies how formal acceptance of the completed project deliverables will be obtained.

17
Q

Components of the requirements management plan can include but are not limited to: (al menos tener idea)

A
  • How requirements activities will be planned, tracked, and reported;
  • Configuration management activities such as: how changes will be initiated; how impacts will be analyzed; how they will be traced, tracked, and reported; as well as the authorization levels required to approve these changes;
  • Requirements prioritization process;
  • Metrics that will be used and the rationale for using them; and
  • Traceability structure that reflects the requirement attributes captured on the traceability matrix.
18
Q

The key benefit of this process is that it provides the basis for defining the product scope and project scope.

A

Collect Requirements

19
Q

It includes conditions or capabilities that are required to be present in a product, service, or result to satisfy an agreement or other formally imposed specification.

A

Requirements

20
Q

enhances brainstorming with a voting process used

to rank the most useful ideas for further brainstorming or for prioritization

A

nominal group technique

21
Q

Visually depict the product scope by showing a business system (process, equipment, computer system, etc.), and how people and other systems (actors) interact with it. It shows inputs to the business system, the actor(s) providing the input, the outputs from the business system, and the actor(s) receiving the output.

A

Context diagrams

22
Q

It´s a method of obtaining early feedback on requirements by providing a model of the expected product before actually building it.

A

Prototyping

23
Q

It´s a prototyping technique showing sequence or navigation through a series of images or illustrations. They´re used on a variety of projects in a variety of industries, such as film, advertising, instructional design, and on agile and other software development projects.

A

Storyboarding

24
Q

Requirements can be grouped into classifications allowing for further refinement and detail as the requirements are elaborated. These
classifications include:

A
o	Business requirements
o	Stakeholder requirements
o	Solution requirements
         Functional requirements
         Nonfunctional requirements
o	Transition and readiness requirements
o	Project requirements
o	Quality requirements
25
Q

It´s a grid that links product requirements from their origin to the deliverables that satisfy them. The implementation helps ensure that each requirement adds business value by linking it to the business and project objectives. It provides a means to track requirements throughout the project life cycle, helping to ensure that requirements approved in the requirements documentation are delivered at the end of the project.

A

Requirements traceability matrix

26
Q

The key benefit of this process is that it describes the product, service, or result boundaries and acceptance criteria.

A

Define Scope

27
Q

Can be used to define products and services. It includes asking questions about a product or service and forming answers to describe the use, characteristics, and other relevant aspects of what is going to be delivered.

A

Product analysis

28
Q

Examples of product analysis techniques include but are not limited to:

A
  • Product breakdown,
  • Requirements analysis,
  • Systems analysis,
  • Systems engineering,
  • Value analysis, and
  • Value engineering.
29
Q

It´s the description of the project scope, major deliverables, assumptions, and constraints. It documents the entire scope, including project and product scope. It describes the project’s deliverables in detail.

A

Project Scope Statement

30
Q

The key benefit of this process is that it provides a framework of what has to be delivered. This process is performed once or at predefined points in the project.

A

Create WBS

31
Q

The planned work is contained within the lowest level of WBS components. It can be used to group the activities where work is scheduled and estimated, monitored, and controlled.

A

work packages

32
Q

It´s a technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.

A

Decomposition

33
Q

Decomposition of the total project work into work packages generally involves the following activities:

A

 Identifying and analyzing the deliverables and related work,
 Structuring and organizing the WBS,
 Decomposing the upper WBS levels into lower-level detailed components,
 Developing and assigning identification codes to the WBS components, and
 Verifying that the degree of decomposition of the deliverables is appropriate.

34
Q

It´s a work breakdown structure component below the control account and above the work package with known work content but without detailed schedule activities.

A

Planning package

35
Q

It´s a document that provides detailed deliverable, activity, and scheduling information about each component in the WBS.

A

The WBS dictionary

36
Q

The key benefit of this process is that it brings objectivity to the acceptance process and increases the probability of final product, service, or result acceptance by validating each deliverable.

A

Validate Scope

37
Q

The key benefit of this process is that the scope baseline is maintained throughout the project.

A

Control Scope

38
Q

The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources is referred to as…

A

scope creep