FLASH_TIME Flashcards

1
Q

ANALYZE PORTFOLIO RISKS

A

The process of prioritizing risks based on probability of occurrence, effect on portfolio goals, organization and stakeholder risk tolerance, and other factors

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

BACKWARDS PASS

A

A network diagramming method that calculates the late start (LS) and late finish (LF) dates for each activity.

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

BAR CHART (Gantt Chart)

A

A chart that shows a time relationship between activites fo the program or project

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

BURST

A

The separation of divergence of activities on a network diagram from a central node

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

COMPONENT MILESTONES

A

Distinguish the deliverables of the program for the purpose of pinpointing milestones for moving component deliverables to the program.

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

CRASHING

A

A duration compression technique in which more people are added to critical path activities to shorten the duration of the critical path or other impacted areas of the schedule

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

CRITICAL PATH

A

The series of activities that shows the overall duration of the program or project; can change as the program or project evolves.

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

CRITICAL PATH METHOD (CPM)

A

A network analysis method used to calculate total program or project duration.

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

DEPENDENCY

A

A relationship between activities represented in the way activities are sequenced.

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

DEVELOP PROGRAM SCHEDULE

A

Process of setting dates for components and milestones. Determine the component execution sequences, estimate the duration of each component, and determine major program milestones, and timing of program packages.

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

DISCRETIONARY DEPENDENCY

A

A dependency in which the Project Manager (or other decision maker) can choose to allow it to be a dependency or not, depending upon the needs of the project; e.g. busying a plane ticket before booking a hotel reservation.

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

DURATION

A

The overall amount of time unexpended on a program or project or activity.

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

EARLY START DATE (ES)

A

The earliest time and activity can start based on the network logic.

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

EARNED FINISH DATE (EF)

A

The earliest time of an activity can finish based on the network logic.

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

ESTIMATE

A

A logical, educated prrediction of some program or project component; typically includes a tolerance of accuracy.

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

EXTERNAL DEPENDENCY

A

A dependency that lies outside the control of the project team.

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

FAST TRACKING

A

A schedule compression technique in which the main focus is to find activities that can be done in parallel and then to adjust the activity sequences to shorten the schedule.

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

FLOAT

A

The amount of time an activity can be delayed or slip without causing a delay to the successor activities or to the final finish date of the program or project.

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

FORWARD PASS

A

A network diagram technique that calculates the arly start (ES) and early (EF) dates for each activity.

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

FREE SLACK (FREE FLOAT)

A

The amount of time an activity can be delayed without causing slippage or delay to the early start of any subsequent activities.

21
Q

GANTT CHART

A

The horizontal bar chart used in program or project management to show a time relationship between activities; also called a bar chart.

22
Q

GERT

A

A diagramming technique that uses fedback loops or multiple passes through a diagram as iterations are completed.

23
Q

LAG

A

A delay to a successor activity from the predessor; e.g., Activity A finishes then has a three-day wait before Activity B can begin

24
Q

LATE FINISH DATE (LF)

A

The latest time an activity can finish without delayign the program or project finish date.

25
Q

LATE START DATE (LS)

A

The latest time an activity can start without delaying the program or project finish date

26
Q

LEAD

A

The act of sequencing activities with an activity that starts before it?s predecessor is 100% complete; elgl, Activity A is four days long, and is followed by Activity B. Activity starts two days after Activity A starts.

27
Q

MANDATORY DEPENDENCY

A

A required dependency on a project; cannot be ignored; e.g. you must pour the foundation of a house before you can begin framing it.

28
Q

MASTER SCHEDULE

A

A high level schedule which displays summary information associated with activities, deliverables, milestones, and WB components.

29
Q

MILESTONE SCHEDULE

A

A high level schedule which displays summary information associated with activities and milestones; also known as milestone chart.

30
Q

MONITOR AND CONTROL PROGRAM SCHEDULE

A

The process of tracking and regulating the timely generation of program deliverables

31
Q

NETWORK DIAGRAM

A

A schematic of logical relationships that make up the flow of activities on the program or projct; always drawn from left to right

32
Q

NETWORK LOGIC

A

The connection of activities on the network diagram to esablish the diagram structure

33
Q

NETWORK PATH

A

A non-stop series of activities from start to fiish o the ntwork diagram

34
Q

NODE

A

A point in a schedule network

35
Q

PATH DIVERGENCE

A

A burst on the network diagram where the output of an activity goes to more than one activity.

36
Q

PREDECESSOR ACTIVITY

A

An activity that determines when its successor activity can begin

37
Q

PROGRAM MASTER SCHEDULE

A

Depicts component schedules and the dependencies between components.

38
Q

PROGRAM SCHEDULE MANAGEMENT PLAN

A

Document that: - decomposes work packages - establishes the network diagram - determines required resources - determines activity duratio - integration activity components into a schedule - considers schedule changes and updates.

39
Q

ROLLING WAVE PLANNING

A

A progressive elaboration approach to managing a schedule where the initial phases are defined at a detailed level with the remaining work at a high level; as the initial phases are done, the remaining phases are planned.

40
Q

SCHEDULE

A

The planned dates, sequencing, resources, and durations of activities and milestones on a program or project.

41
Q

SCHEDULE COMPRESSION

A

The process of shortening the program or project schedule without modifying the scope of the program or project; e.g., crashing and fast tracking

42
Q

SLACK (FLOAT)

A

The amount of time an activity can be delayed or slip without causing a delay to the successor activities or to the final program or project finish date.

43
Q

SUCCESSORY

A

An activity that follows a logically connected activity

44
Q

THREE POINT ESTIMATE

A

An estimating technique that can be applied to schedule or budget and uses three estimates for each activity; optimistic; pessimistic, and realistic.

45
Q

TOTAL FLOAT (TF)

A

The maximum amount of time an activity can slip without causing a delay to the program or project finish date.

46
Q

TOTAL SLACK (TOTAL FLOAT)

A

The amount of time an activity can slip or be delayed from its arly start date without delaying the overal finish date.

47
Q

VARIANCE

A

A result that varies from the expected result.

48
Q

RESOURCE LEVELING PURPOSES (2)

A
  1. Approach to show the impact on the schedule if the resources are not available as planned.
  2. Way to optimize the program plan by leveling the resource requirements in order to gain efficiencies and maximize productivity/synergies amongst projects