Brainscape's Knowledge GenomeTM

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


See full index

PMP Exam BL > 5. Scope > Flashcards

5. Scope Flashcards

1
Q

What is a baseline

A

Whether for scope, schedule, cost or quality, a baseline is the original plan plus all approved changes.

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

What is the scope baseline?

A 
Represents the combination of: 
• Project scope statement
• WBS
• WBS dictionary
• Work package 
• Planning package.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is Project Scope Management?

A

Project Scope Management 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 the project scope is primarily concerned with defining and controlling what is and is not included in the project.

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

What are the Project Scope Management processes?

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

Define the process of Collect Requirements?

A

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

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

Define the process of Define Scope?

A

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

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

Define the process of Create WBS?

A

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

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

Define the process of Validate Scope?

A

The process of formalising acceptance of the completed project deliverables.

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

Define the process of Control Scope?

A

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

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

What is a product backlog?

A

The overall scope of an adaptive project decomposed into a set of requirements and work to be performed

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

In an adaptive process, which are the Scope processes that are repeated for each iteration?

A
  • 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
12
Q

Definition of “requirement” for project or product requirement

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.

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

What is the Plan Scope Management process?

A

Plan Scope Management is the process of creating a scope management plan that documents how the project and product scope will be defined, validated, and controlled. The key benefit of this process is that it provides guidance and direction on how scope will be managed throughout the project.

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

What are the inputs of the Plan Scope Management Process?

A
  1. Project Charter
  2. Project Management plan
    • Quality management plan
    • Project life cycle description
    • Development approach
  3. Enterprise environmental factors
  4. Organisational process assets
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the outputs of the Plan Scope Management process?

A
  1. Scope management plan

2. Requirements management plan

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

What are the components of a scope management plan?

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

What is the requirements management plan?

A

The requirements management plan is a component of the project management plan that describes how project and product requirements will be analysed, documented, and managed.

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

What are the enterprise environmental factors that can influence the Plan Scope Management process?

A
  • Organisational culture,
  • Infrastructure,
  • Personnel administration, and
  • Marketplace conditions.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What are the organisational process assets that can influence the Plan Scope Management process?

A
  • Policies and procedures, and

* Historical information and lessons learned repository with information from previous projects.

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

What is Product Scope?

A

Requirements that relate to the product, service, or result of the project. Product deliverables with their associated features and functions.

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

What is Project Scope?

A

Work the project team will do to deliver the product of the project, it encompasses the product scope. It includes the planning, coordination, and management activities that ensure the product scope is achieved.

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

What is the Collect Requirements process?

A

Collect requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet objectives. The key benefit of this process is that it provides the basis for defining the product scope and project scope.

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

What are the inputs of the Collect requirements Process?

A
  1. Project Charter
  2. Project management plan
    • Scope management plan
    • Requirements management plan
    • Stakeholder engagement plan
  3. Project documents
    • Assumption log
    • Lessons learned register
  4. Business documents
    • Business case
  5. Agreements
  6. Enterprise environmental factors
  7. Organisational process assets
24
Q

What are the outputs of the Collect Requirements process?

A
  1. Requirements documentation

2. Requirements traceability matrix

25
Q

What are the other parts of the project impacted by the requirements?

A
  • Foundation of the WBS
  • Cost
  • Schedule
  • Quality planning
  • Procurement
26
Q

What are the enterprise environmental factors that can influence the Collect Requirements process?

A
  • Organisational culture,
  • Infrastructure,
  • Personnel administration, and
  • Marketplace conditions.
27
Q

What are the organisational process assets that can influence the Collect Requirements process?

A
  • Policies and procedures, and

* Historical information and lessons learned repository with information from previous projects.

28
Q

What is the Define Scope process?

A

Define Scope is the process of developing a detailed description of the project and product. The key benefit of this process is that it describes the product, service, or result boundaries and acceptance criteria.

29
Q

What are the inputs of the Define Scope Process?

A
  1. Project charter
  2. Project management plan
    • Scope management plan
  3. Project documents
    • Assumption log
    • Requirements documentation
    • Risk register
  4. Enterprise environmental factors
  5. Organisational process assets
30
Q

What are the outputs of the Define Scope process?

A
  1. Project scope statement
  2. Project documents updates
    • Assumption log
    • Requirements documentation
    • Requirements traceability matrix
    • Stakeholder register
31
Q

What is Acceptance criteria?

A

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

32
Q

What are the contents of the Scope Statement?

A
  • Product scope description. Progressively elaborates the characteristics of the product, service, or result described in the project charter and requirements documentation.
  • Deliverables. 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. Deliverables also include ancillary results, such as project management reports and documentation. These deliverables may be described at a summary level or in great detail.
  • Acceptance criteria. A set of conditions that is required to be met before deliverables are accepted.
  • Project exclusions. Identifies what is excluded from the project. Explicitly stating what is out of scope for the project helps to manage stakeholder’s expectations and can reduce scope creep.
  • Constraints and Assumptions.
33
Q

What is the WBS process?

A

Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components. The key benefit of this process is that it provides a framework of what has to be delivered.

34
Q

What are the inputs of the Create WBS Process?

A 
1. Project management plan
     • Scope management plan
2. Project documents
     • Project scope statement
     • Requirements documentation
3. Enterprise environmental factors
4. Organisational process assets
35
Q

What are the outputs of the Create WBS process?

A
  1. Scope baseline
  2. Project documents updates
    • Assumption log
    • Requirements documentation
36
Q

What are the activities involved in the decomposition of project work?

A
  • Identifying and analysing the deliverables and related work,
  • Structuring ad organising 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.
37
Q

In what forms the WBS can be represented?

A
  • Using phases of the project life cycle as the second level of decomposition, with the product and project deliverables inserted at the third level;
  • Using major deliverables as the second level of decomposition; and
  • Incorporating subcomponents that may be developed by organisations outside the project team, such as contracted work. The seller then develops the supporting contract WBS as part of the contracted work.
38
Q

What is a work package?

A

A work package is the smallest unit of a Work Breakdown Structure. When preparing a Work Breakdown Structure using the decomposition technique, deliverables are generally broken down into smaller, more manageable chunks of work.
This process of deconstruction continues until the deliverables are small enough to be considered work packages. Each of these packages should be small enough to help the Project Manager estimate the duration and the cost. Work packages can be scheduled, cost estimated, monitored, and controlled.
Work package is the smallest deliverable in WBS. Tasks are not part of the WBS.

39
Q

WBS. What is a control account?

A

Each work package is part of a control account. A control account is a management control point where scope, budget, and schedule are integrated and compared to the earned value for performance measurement. A control account has two or more work packages, though each work package is associated with a single control account.

40
Q

WBS. What are the codes of accounts?

A

Code of Accounts is a numbering system that uniquely identifies each component of the WBS

41
Q

WBS. What is a planning package?

A

A control account may include one or more planning packages. A planning package is a work breakdown structure component below the control account and above the work package with known work content but without detailed schedule activities.

42
Q

What is a WBS dictionary?

A

The WBS dictionary is a document that provides detailed deliverable, activity, and scheduling information about each component in the WBS. The WBS dictionary is a document that supports the WBS. Most of the information included in the WBS dictionary is created by other processes and added to this document at a later stage.

43
Q

What information is included in the WBS dictionary?

A 
o Code of account identifier,
o Description of work,
o Assumptions and constraints,
o Responsible organisation,
o Schedule milestones,
o Associated schedule activities,
o Resources required,
o Cost estimates,
o Quality requirements,
o Acceptance criteria,
o Technical references, and
o Agreement information.
44
Q

What is the Validate Scope process?

A

Validate scope is the process of formalising acceptance of the completed project deliverables. 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.

45
Q

What are the inputs of the Validate Scope Process?

A 
1. Project management plan
     • Scope management plan
     • Requirements management plan
     • Scope baseline
2. Project documents
     • Lessons learned register
     • Quality reports
     • Requirements documentation
     • Requirements traceability matrix
3. Verifiable deliverables
4. Work performance data
46
Q

What are the outputs of the Validate Scope process?

A
  1. Accepted deliverables
  2. Work performance information
  3. Change requests
  4. Project document updates
    • Lessons learned register
    • Requirements documentation
    • Requirements traceability matrix
47
Q

What is the Control Scope process?

A

Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. The key benefit of this process is that the scope baseline is maintained throughout the project.

48
Q

What are the inputs of the Control Scope Process?

A 
1. Project management plan
     • Scope management plan
     • Requirements management plan
     • Change management plan
     • Configuration management plan
     • Scope baseline
     • Performance measurement baseline
2. Project documents
     • Lessons learned register     
     • Requirements documentation
     • Requirements traceability matrix
3. Work performance data
4. Organisational process assets
49
Q

What are the outputs of the Control Scope process?

A
  1. Work performance information
  2. Change requests
  3. Project management plan updates
    • Scope management plan
    • Scope baseline
    • Schedule baseline
    • Cost baseline
    • Performance measurement baseline
  4. Project documents updates
    • Lessons learned register
    • Requirements documentation
    • Requirements traceability matrix
50
Q

What is scope creep?

A

The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources

51
Q

What is Management By Objectives (MBO)?

A

It is an agreed-upon work goal where both the Manager and contributor agree to both the product and process involved in realising the deliverable. MBO lends itself well to the WBS type of work definition.

52
Q

What is the Code of Accounts?

A

The numbering system used to uniquely identify each component of the work breakdown structure WBS.

53
Q

What are the contents of the Requirements Traceability Matrix?

A
  • Requirement description
  • Req ID
  • Source/requestor
  • Business justification / RFP
  • WBS task
  • Status
54
Q

What the Requirements Traceability Matrix is used for?

A
  • Track all requirements and whether or not they are being met by the current process and design
  • Assist in the creation of the RFP, Project Plan Tasks, Deliverable Documents, and Test Scripts
  • Help ensure that all system requirements have been met during the Verification process.
55
Q

What are the common causes of scope creep?

A
  • Lack of formal requirements management
  • Inconsistent processes for collecting requirements
  • Lack of stakeholder involvement
  • Project length
56
Q

What is product analysis and what are the main techniques?

A 
Product analysis can be used as a tool to define the scope of a project. It involves methods for translating high-level product or service descriptions into meaningful deliverables. Examples of techniques:
• Product breakdown
• Requirement analysis
• Systems analysis
• Systems engineering
• Value analysis
• Value engineering

PMP Exam BL (13 decks)

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