Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

CONSTRUCTION METHODS AND PROJECT MANAGEMENT > CHAPTER 5 PMBOK > Flashcards

CHAPTER 5 PMBOK Flashcards

1
Q

Includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully

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

Plan Scope Management;
Collect Requirements;
Define Scope;
Create WBS;
Validate Scope;
Control Scope

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

In the project context, the term “scope” can refer to:

A

Product scope
Project scope

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

Can range along a continuum from predictive approaches at one end to adaptive or agile approaches at the other

A

Project Life Cycle

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

The deliverables are developed over multiple iterations where a detailed scope is defined and approved for each iteration when it begins

A

Adaptive/Agile Life Cycle

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

Three processes of adaptive life cycle iteration

A

Collect Requirements;
Define Scope;
Create WBS

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

in a predictive project, these processes are performed toward the beginning of the project and updated as necessary

A

Integrated Change Control Process

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

Overall scope of an adaptive project will be decomposed into a set of requirements and work to be performed.

A

Product backlog

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

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
10
Q

Is 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
11
Q

True or False: The relationship between a project manager and a business analyst should be a collaborative partnership

A

True

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

Considerations for tailoring include but are not limited to:

A

Knowledge & requirements management
Validation and control
Development approach
Stability of requirements
Governance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
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
14
Q

Documents the project purpose, high

A

Project Charter

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

A component of the project or program management plan that describes how the scope will be defined, developed, monitored, controlled, and validated

A

The scope management plan

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

Components of project management plan:

A

Quality Management Plan;
Project life cycle description;
Development approach

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

A component of the project management plan that describes how project and product requirements will be analyzed, documented, and managed; some organizations refer to it as a business analysis plan

A

Requirements management plan

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

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

A

Collect Requirements

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

Documents the high

A

Project Charter

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

Components of a Project Charter

A

Stakeholder engagement plan

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

Is used to understand stakeholder communication requirements and the level of stakeholder engagement in order to assess and adapt to the level of stakeholder participation in requirements activities

A

Scope Management Plan
Requirements management plan
Stakeholder engagement plan

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

Project Documents include:

A

Assumption Log
Lessons learned register
Stakeholder Register

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

Identified assumptions about the product, project, environment, stakeholders, and other factors that can influence requirements

A

Assumption Log

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

Is used to provide information on effective requirements collection techniques, especially for projects that are using an iterative or adaptive product development methodology

A

Lessons learned register

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

Is used to identify stakeholders who can provide information on the requirements. It also captures requirements and expectations that stakeholders have for the project.

A

Stakeholder Register

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

Data Gathering Techniques:

A

Brainstorming
Interviews
Focus Groups
Questionnaires and surveys
Benchmarking

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

Are written sets of questions designed to quickly accumulate information from a large number of respondents; most appropriate when respondents are geographically dispersed

A

Questionnaires and surveys

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

Involves comparing actual or planned products, processes, and practices to those of comparable organizations to identify best practices, generate ideas for improvement, and provide a basis for measuring performance

A

Benchmarking

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

Consists of reviewing and assessing any relevant documented information; used to elicit requirements by analyzing existing documentation and identifying information relevant to the requirements

A

Document analysis

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

Decision Making Techniques:

A

Voting (Unanimity, Majority, Plurality)
Autocratic decision making
Multicriteria decision analysis

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

A collective decision

A

Voting

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

A decision that is reached whereby everyone agrees on a single course of action

A

Unanimity

33
Q

A decision that is reached with support obtained from more than 50% of the members of the group

A

Majority

34
Q

A decision that is reached whereby the largest block in a group decides, even if a majority is not achieved. This method is generally used when the number of options nominated is more than two

A

Plurality

35
Q

In this method, one individual takes responsibility for making the decision for the group

A

Autocratic decision making

36
Q

A technique that uses a decision matrix to provide a systematic analytical approach for establishing criteria, such as risk levels, uncertainty, and valuation, to evaluate and rank many ideas

A

Multicriteria decision analysis

37
Q

Data Representation Techniques:

A

Mind mapping

38
Q

Allow large numbers of ideas to be classified into groups for review and analysis

A

Affinity diagrams

39
Q

Consolidates ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas

A

Mind mapping

40
Q

Interpersonal and Team Skills:

A

Nominal group technique
Observation/conversation
Facilitation

41
Q

Enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization

A

Nominal group technique

42
Q

Provide a direct way of viewing individuals in their environment and how they perform their jobs or tasks and carry out processes

A

Observation/conversation

43
Q

Is used with focused sessions that bring key stakeholders together to define product requirements

A

Facilitation

44
Q

can be used to quickly define cross

A

Workshops

45
Q

Facilitation skills are used in the following situations, but are not limited to:

A

Joint application design/development (JAD);
Quality function deployment (QFD);
User stories

46
Q

These facilitated sessions focus on bringing business subject matter experts and the development team together to gather requirements and improve the software development process

A

Joint application design/development (JAD) sessions

47
Q

Another facilitation technique that helps determine critical characteristics for new product development

A

Quality function deployment (QFD)

48
Q

Are short, textual descriptions of required functionality, are often developed during a requirements workshop

A

User stories

49
Q

Example of a scope model; 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

A

Context Diagram

50
Q

A method of obtaining early feedback on requirements by providing a model of the expected product before actually building it

A

Prototyping

51
Q

A prototyping technique showing sequence or navigation through a series of images or illustrations

A

Storyboarding

52
Q

Outputs for the Collect Requirements process:

A
  1. Business requirements
  2. Stakeholder requirements
  3. Solution requirements
    4.Transition and readiness requirements
  4. Project requirements
  5. Quality requirements
53
Q

These describe the higher

A

Business requirements

54
Q

These describe needs of a stakeholder or stakeholder group

A

Stakeholder requirements

55
Q

These describe features, functions, and characteristics of the product, service, or result that will meet the business and stakeholder requirements. Can be grouped into functional and nonfunctional requirements

A

Solution requirements

56
Q

Describe the behaviors of the product

A

Functional Requirements

57
Q

Supplement functional requirements and describe the environmental conditions or qualities required for the product to be effective

A

Nonfunctional Requirements

58
Q

These describe temporary capabilities, such as data conversion and training requirements, needed to transition from the current as

A

Transition and readiness requirements

59
Q

These describe the actions, processes, or other conditions the project needs to meet. Examples include milestone dates, contractual obligations, constraints, etc.

A

Project requirements

60
Q

These capture any condition or criteria needed to validate the successful completion of a project deliverable or fulfillment of other project requirements

A

Quality requirements

61
Q

A grid that links product requirements from their origin to the deliverables that satisfy them

A

The Requirements traceability matrix

62
Q

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

A

Define Scope

63
Q

The risk register contains response strategies that may affect the project scope, such as reducing or changing project and product scope to avoid or mitigate a risk

A

Risk register

64
Q

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

A

Project scope statement

65
Q

Progressively elaborates the characteristics of the product, service, or result described in the project charter and requirements documentation

A

Product scope description

66
Q

Any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project

A

Deliverables

67
Q

A set of conditions that is required to be met before deliverables are accepted

A

Acceptance criteria

68
Q

Identifies what is excluded from the project

A

Project exclusions

69
Q

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

A

Create WBS

70
Q

Is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables

A

WBS (Work Breakdown Structure)

71
Q

The work defined at the lowest level of the WBS for which cost and duration can be estimated and managed

A

Work packages

72
Q

refers to work products or deliverables that are the result of activity and not to the activity itself

A

Work

73
Q

A technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts

A

Decomposition

74
Q

True or False: Excessive decomposition can lead to nonproductive management effort, inefficient use of resources, decreased efficiency in performing the work, and difficulty aggregating data over different levels of the WBS

A

True

75
Q

___________ is 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

76
Q

___________ is a document that provides detailed deliverable, activity, and scheduling information about each component in the WBS

A

WBS dictionary

77
Q

____________ is the process of formalizing acceptance of the completed project deliverables

A

Validate Scope

78
Q

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

A

Control scope

CONSTRUCTION METHODS AND PROJECT MANAGEMENT (2 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions