Capm-Scope

Front 1

Key outputs when planning your project scope?

Back 1

requirements documentation, project scope statement, scope baseline and WBS; you need to reference your scope management plan to define, develope, validate manage and control scope.

Front 2

What is product scope?

Back 2

what the project is creating

Front 3

What is project scope?

Back 3

The work required to create the project results

Front 4

Process - Plan scope management

Back 4

In the PLANNING process group. It emphasis the creation of the scope management plan;

Front 5

What is the Scope management plan?

Back 5

Contributes to the management and definition of the project by defining how scope will be managed. It guides: requirements gathering, scope statement, WBS, and validation and control of the scope of the project. It defines how we will: create a scope statement, create a WBS, validate project deliverables, address scope change requests

Front 6

Process - Plan scope management: inputs

Back 6

Project management plan; project charter

Front 7

Process - Plan scope management: tools and techniques

Back 7

Expert judgement

Front 8

Process - Plan scope management: outputs

Back 8

Scope management plan; Requirements management plan

Front 9

Project charter

Back 9

the high-level description of the project and product details.

Front 10

Scope creep

Back 10

The risk of unmanaged scope expansion due to not making use of the Scope management plan defined in the Plan Scope Management process

Front 11

What is the Requirements management plan?

Back 11

It helps theproject manager and team analyze, document and manage the project requirements. It defines how we will: manage requirements, create requirements, plan+track+report requirement activity, perform configuration management activities, initiate changes to the product or service or result, analyze the impact of requirement changes, change approval authorization, prioritize requirements, determine product metrics and usage rationale, define the traceability structure for the requirements traceability matrix and traceability to any other requirements-related documentation

Front 12

Process - Collect Requirements

Back 12

In the PLANNING process group. It emphasis the creation of requirements based on the analysis of sponsor, customer or stakeholder needs; Rrequirements feed the WBS and factor into Quality, schedule and cost estimates; begins with the analysis of the project charter and stakeholder register;

Front 13

Process - Collect Requirements: inputs

Back 13

Scope management plan; requirements management plan; stakeholder management plan; project charter; stakeholder register

Front 14

Process - Collect Requirements: tools and techniques

Back 14

Interviews; facilitated workshops, focus groups; group creativity techniques; observations; group decision-making techniques; prototypes; questionnaires and surveys; benchmarking; context diagrams;

Front 15

Process - Collect Requirements: outputs

Back 15

Requirements documentation; Requirements traceability matrix

Front 16

What are some Group Creativity Techniques?

Back 16

brainstorming; nominal group technique; multiple criteria decision analysis; idea/mind mapping; affinity diagrams

Front 17

What is a Requirements traceability matrix?

Back 17

A document that itemizes each requirement and associates it to the detailed and high-level requirements documentation where it was discovered and defined as well as to any design, implementation or test documentation

Front 18

Process - Define scope

Back 18

In the PLANNING process group; It emphasises writing the scope statement used in future decision-making and should include: what the project consists of; what is involved to create the project; and what it is expected to provide/do once it is complete

Front 19

Process - Define scope: inputs

Back 19

Scope management plan; Project charter; Requirements documentation

Front 20

Process - Define scope: tools and techniques

Back 20

Expert judgement, product analysis; alternatives generation; facilitated workshops

Front 21

Process - Define scope: outputs

Back 21

project scope statement

Front 22

What is product analysis?

Back 22

It translates product descriptions into actual deliverables

Front 23

What is Alternatives generation?

Back 23

brainstorming and lateral thinking to indentify approach alternatives in how you approach the execution and performance of the project

Front 24

What is the Project Scope Statement?

Back 24

Defines the project in terms of it's scope, key deliverables, product acceptance criteria, exclusions, assumptions and constraints; It facilitates team project planning and identifies stakeholder expectations;

Front 25

What makes up the Project Scope Statement?

Back 25

Typically consists of: product scope description (progresively elaborated), product acceptance criteria, project deliverables, project exclusions, project contraints and assumptions

Front 26

Process - Create WBS

Back 26

In the PLANNING process group; It emphasises breaking down the project into pieces that can be easily tracked;

Front 27

What is Rolling wave planning?

Back 27

Project planning that is progressively elaborated as additional requirements become more clear; It is used when initial project decomposition is unable to break down deliverable requirments due to a lack of information

Front 28

Process - Create WBS: inputs

Back 28

Scope management plan, project scope statement, requirements documentation

Front 29

Process - Create WBS: tools and techniques

Back 29

Decomposition (breaking down scope and requirements into manageable pieces)

Front 30

Process - Create WBS: outputs

Back 30

Scope baseline (the details of the planned scope of the project) which includes the approved: project scope statement, WBS and WBS dictionary

Front 31

What is the WBS?

Back 31

Work breakdown structure; The team defines the main pieces of the project work, decomposing them into WORK PACKAGES (the lowest level of the WBS, often deliverables) and possibly down to activity lists; teams working on this creates buy-in from team members

Front 32

What are the main pieces of a WBS?

Back 32

control accounts, planning packages, and work packages

Front 33

What is a control account?

Back 33

A management control point that represents a collection of one or more work packages; it acts like a management milestone with rolled up scope, time and cost.

Front 34

What is a work package?

Back 34

A work package is an estimated (level of effort in terms of: cost, time, and scope) for a descrete piece of work in the project

Front 35

What is the 100% rule?

Back 35

!00% of the project work needs to be represented in the WBS (from admin to testing)

Front 36

What is WBS numbering?

Back 36

It lets team members know where work fits into the project

Front 37

What is the WBS dictionary?

Back 37

Provides supporting details for each WBS item that is typically not practical to put into the graphical format of the WBS. The WBS dictionary typically includes: code of accounts, list of schedule milestones, cost estimates, description of work, associated sceduled activities, quality requirements, contract information, responsible organization, resources required, acceptance criteria

Front 38

What is the Organizational breakdown structure?

Back 38

Shows how the project organization is structured in terms of human resources, to accomplish project activities

Front 39

What is the Risk breakdown structure?

Back 39

Shows the potential project risk broken down by risk category

Front 40

What is the Resource breakdown structure?

Back 40

Shows the types of resources used in the project

Front 41

What is the Bill of materials?

Back 41

Includes components, sub-assemblies and assemblies used to build a product or service

Front 42

Process - Validate Scope

Back 42

In the MONITORING AND CONTROLLING process group; Used to secure sign-off of project scope at logical intervals during the process (milestones, each deliverable, possibly each phase, when the work is complete, etc)

Front 43

Process - Validate Scope: inputs

Back 43

Project management plan; requirements documentation; requirements traceability matrix; verified deliverables; work performance data

Front 44

Process - Validate Scope: tools and techniques

Back 44

Inspection (to measure, examine and validate that the work and deliverables fulfill the requirements)

Front 45

Process - Validate Scope: outputs

Back 45

Accepted deliverables; change requests (not yet approved)

Front 46

Process - Control Scope

Back 46

in the MONITORING AND CONTROLLING process group; proces for handling any scope change requests and related matters

Front 47

Process - Control Scope: inputs

Back 47

Project management plan; Requirements documentation; requirements traceability matrix; work performance data

Front 48

Process - Control Scope: tools and techniques

Back 48

Variance Analysis

Front 49

Process - Control Scope: outputs

Back 49

Work performance information; Change requests

Front 50

What is Variance analysis?

Back 50

it determines the difference between the original scope baseline and actual performance.

Front 51

What is Work performance data?

Back 51

The raw data coming from people executing activities in the EXECUTING process group

Front 52

Work is Work performance information?

Back 52

The reports generated from having analyzed work performance data