SCOPE MGMT Flashcards Preview

PgMP > SCOPE MGMT > Flashcards

Flashcards in SCOPE MGMT Deck (62):
1

ACCEPTANCE

The process of formally receiving the work of the project after it is determined that the work is complete and fulfills the needs for which it was created.

2

ACCEPTANCE CRITERIA

Requirements that must be completed before th work can be accepted

3

BENEFITS REALIZATION PLAN

The document that memoriatizes the proposed benefits of the program for team monitoring, distinguishes the process and systems needed to achieve the benefits, details the manner in which the benefits will be achieved, and develops the schedule for transitioning the benefits

4

BILL OF MATERIALS (BOM)

A formal document showing the heirarchy of product components or pieces and their subcomponents or sub-pieces

5

COMPONENT STAKEHOLDER MANAGEMENT GUIDELINES

The blue print for managing stakeholders at the component level which addresses identification, assessment, and involvement of the stakeholders

6

CONTROL ACCOUNT

A point where scope, time, budgeted cost, and actual cost come together to measure performance on a program or project; the control account is used at multiple interface points on the program or project

7

DECOMPOSITION

The process of breaking down the work of the program or project into smaller more controllable pieces

8

DEFINE PROGRAM GOALS AND OBJECTIVES

The process of determining the program objectives and benefits

9

DELIVERABLE

A key piece of work for the program or project; can be physical work, a process, a document, or other measurable result of work

10

DEVELOP PROGRAM ARCHITECTURE

The process of evolving the framework of the program components and determining the interrelationships of the components

11

DEVELOP PROGRAM REQUIREMENTS

The process of determining and evolving the requirements that will attain the program objectives

12

DEVLOP PROGRAM WBS

The process of decomposing the program to its components, deliverables, and activities to generate a work breakdown structure for each program components

13

FOCUS GROUPS

Groups comprised of individuals who are brought together to answer specific questions about their reactions to a product, service, or idea; problem solving is often a goal of focus groups

14

MANAGE PROGRAM ARCHITECTURE

Manages the relationships across all program components to ensure that the program architecture remains consistent across all the deliverables.

15

MANAGEMENT COMPONENT INTERFACES

The process of ensuring that program components are executed so that program benefits are delivered

16

MILESTONE

A major achievement on a program or project resulting from the completion of a series of activities; has ero=days duration and could be related to a "deliverable"

17

MONITOR AND CONTROL PROGRAM SCOPE

The process of tracking and regulating the program to ensure adherence to the program charter in terms of objectives and benefits

18

PLAN PROGRAM SCOPE

The process of distinguishing and evolving the activities that will produce the benefits and objecties defined in the program charter

19

PROGRAM ARCHITECTURE

The coherent structure and interrelationship of the products of program component. The structure of the program component products and their technical relationships with one another

20

PROGRAM ARCHITECTURE BASELINE

Comprised of the components that provide the specified benefits of the program and delineates their attributes, skills, timing and external interactions.

21

PROGRAM DOCUMENT REPOSITORY

provides storage and accessiblity for program related documents; typically, versioning and standard document format are considered in the design

22

PROGRAM REQUIREMENTS DOCUMENT

Depicts requirements that deliver benefits and addresses enterprise, environmental, legal, and technical consequences

23

PROGRAM SCOPE MANAGEMENT PLAN

Part of program plan containing: 1. Assessment of scope stability, 2. Processes for Scope Change Req, 3. Processes to ID scope changes, 4. How scope managed, 5. How to integrate changes

24

PROGRAM WORK BREAKDOWN STRUCTURE (PWBS)

An organized breakdown of the total work scope of the program, with each level of descent providing a greater level of detail

25

PROJECT SCOPE BASELINE

Original, or revised with proper authorization, definition of the scope of the project; can include project scope statement, work breakdown structure (WBS), and WBS dictionary

26

PWBS DICTIONARY

Description of components and relevant info such as: Logical groupings, Interfaces with ops or products, Clarify program?s conclusion, Non-project related work done at program level

27

REQUESTED CHANGE

A formal request for a change to the program or project that is submitted for approval

28

REQUIREMENT

A business or technical requirement for the attainment of program or project goals

29

SCOPE

The work that will be encompassed in the program or project and the final product, service, result, or benefit. Scope overview and lists: 1. Org needs and requirements 2. High-level product requirements 3. Solution vision 4. Assumptions, Constraints, & Risks 5. Desc. of each project & resources 6. program Benefits and Deliverables

30

SCOPE CHANGE

An approved change to the scope of the program or project

31

SCOPE CREEP

unauthorized request for changes that occur as the program or project evolves

32

SCOPE STATEMENT

Written statement in Pg Mgmt Plan which includes: 1) What is/is not included 2) List of Deliverables and Success Criteria 3) what the program is expected to do when complete. Used to gain common buyin from stakeholders on what the program is. Includes: detailed description of constraints, requirements, scope, business effect the program will have, description of each component, and a description of resources for each components
- The stakeholders "sign off" on this for alignment.

33

STATEMENT OF WORK (SOW)

a description of services, products, and work results to be accomplished on a project or other initiative

34

TASK

an activity to be completed on the program or project

35

TASK RESPONSIBILITY MATRIX

an array of roles and involvement levels of each team member

36

VALIDATION

the process of evaluating something that was created in the program or project to ensure that it meets the requirements for formal acceptance

37

VERIFICATION

the process of evaluating something that was created in the program or project to ensure that it meets the specified conditions

38

WORK BREAKDOWN STRUCTURE MATRIX

an array of work elements used to organize and categorize work scope

39

WORK PACKAGE

a deliverable at the smallest level of the PROJECT WBS; represents the completed piece of the project from the culmination of a series of activiteis being complete

40

How does the Program Mgmt Plan help the PgM?

1. Establish a cope statement and requirements 2) creeate a PWBS, 3) validate that the deliverables and work of the program were built correclty and 4) address cope-related changes to the program and its projects

41

CUSTOMER ACCEPTANCE REVIEW

Tool used during "Define Pg Goals and Obj" process in order to obtain customer acceptance for each deliverable to ensure custoemr satisfaction in the end.

42

REQUIREMENTS GATHERING

tool used during "develop requirements". Method of assembling requirements from various sources, including stakeholders, existing documents, and process anlayis; methods include inteerviewing, focus groups, and surveys.

43

REQUIREMENTS ANALYSIS

tool used during "develop requirements". Method of assessing the requirements to ensure consistency and completeness

44

DESIGN REVIEW

tool used during "develop requirements". Review to determine that the design of the program or component meets best practice guidelines; design reviews may be formal, reviewed by the customer, internal, reviewd by subject matter experts and peers, or in-process, reviewed by peers

45

BRAINSTORMING

tool used during "develop requirements". Used to ID requirements often.

46

REQUIREMENTS VERIFICATION AND VALIDATION

tool used during "develop requirements". Ongoing process of determining that requirements are correct and comprehensive.

47

COMPONENT REQUIREMENTS DOC

Output of "develop requirements". Decomposes component needs for inclusion into contracts and further decomposes them to a level that allows accurate schedule estimates.

48

MANAGEMENT PLANNING PROCESSES

tool used during "Develop PWBS". Supplies assessment and conception methods for achieving the program goals.

49

SYSTEM CONFIGURATION TOOLS

tool used during "Develop PWBS". Provide change control for items, such as processes, that are subject to modification throughout the program life cycle; the tools assign version control for ease of monitoring change.

50

Who creats the PWBS?

PgM, Program Team, Project Mgrs, and PM teams

51

What items are able to start from the PWBS?

schedule, bugt, resource assignments, risk planning

52

How many levels of the Project WBS are typically included in the PWBS?

the top 2

53

What happens with inadequate PWBSS work?

often leads to scope creep and estimating inaccuracies. Jeapordizes successful delivery of one or more projects

54

Organizational Breakdown Structure

also known as an org chart for the program

55

RBS (Resource Breakdown Structure)

shows the type of resources used on a program or project

56

CONFLICT MANAGEMENT

Conflict management is the approach used to resolve conflict among stakeholders and team members; escalation is addressed in conflict management

57

VERIFY SCOPE

process that occurs during project mgmt. used to approve copmleted project deliverables that contribute to benefits at the program level.

58

100% RULE

ensuring that 100% of the work of the program or project is represented in the WBS to ensure that the time, cost, and staffing estimates are as accurate as possible.

59

PROGRAM PACKAGE

lowest level of decomposition at the PROGRAM LEVEL.

60

M/C SCOPE OUTPUTS (4)

1. Approved Change Requests - governance group approves scope change formally
2. Pg Requirements Updates - as needed per the approved change
3. Pg Mgmt Plan Updates - as needed per the approved change
4. Pg Doc Repository Updates - must update the docs accordingly per the change!

61

M/C SCOPE INPUTS (6)

1. Pg Scope Statement - current approved scopes, constraints, requirements
2. Scope Change Requests - requests
3. Component Transition Requests - after governance review, Pg mgr does final confirmation scope of components complete
4. Pg Architcture Baseline - review for timing of components, etc. Are things progressing? how will the change requests affect this?
5. Governance Plan - tells processes to follow for change requests, initiate comp, etc
6. Pg Mgmt Plan - Provides overall plan for M/C

62

END USER VS CUSTOMER STAKEHOLDERS

The customer is the one contracting with you for the product or service. But the End User is the ultimate final user after the product/service is resold to them. The PgM should meet with end-users as much as feasible to understand the ultimate product/service requirements.