6 - Schedule Management Flashcards

1
Q

Activity List

A

Primary output of breaking down the WBS work packages

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

Alternative Analysis

A

Identification of more than one solution.

Consider: roles, materials, tools, approaches to project work.

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

Analogous Estimating

A

Like an analogy.

Estimating approach that relies on historical information (expert judgement).

Unreliable but fast. More reliable than team member recollections.

aka top down estimating

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

Bottom-up estimating

A

Estimating approach where you start at the bottom and estimate time for each activity., its predecessor and its successor.

Most accurate time-and-cost estimating.

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

Control account

A

A management control point where scope, budget, and schedule are integrated and compared to the earned value for performance measurement.

A WBS entry that considers time, cost, scope meaurements for that deliverable. Above Work Package in hierarchy.

Estimated performance compared against actual performance to measure overall performance for the deliverables within that control account.

Specifics documented in control account plan.

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

Control Threshold

A

Predetermined range of acceptable variances e.g. +/- 10%.

If variance exceeds this, project control processes and corrected actions enacted.

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

Crashing

A

Scheudle compression where more resources are added to complete project earlier.

Added costs. Law of diminishing returns could apply here.

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

Critical path

A

The path in the network diagram that cannot be delayed otherwise project completion will be late.

Activities in critical path have no float.

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

Discretionary dependencies

A

Preferred order of activities.

PMs should use these relationships at their discretion and should document logic.

Allow activities to happen in preferred order because of best practices, conitions uniqyue to project, or external events.

AKA preferential or soft logic.

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

Early Finish

A

Earliest an activity can finish. Used in forward pass procedure to discover the critical path and the project float.

top right in network diagram node.

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

Early start

A

Earliest an activity can begin. Used in forward pass procedure to discover the critical path and the project float.

Top left in network diagram node.

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

External dependencies

A

Dependencies outside project’s control.

e.g. decision of committee, delivery of equipment, etc.

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

Fast-tracking

A

A schedule compression method that changes relatioships of activities.

Sequential activities allowed to operate in parallel or with overlap.

FS to SS or FF, or by adding lead time to downstream activities.

Added risk.

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

Finish to finish

A

FF

Activity relationship that requires current activity to be finished before the successor can finish.

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

Finish to start

A

FS

Activity relationship:
current activity must finish before successor can start.

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

Fragnet

A

Representation of project network diagram that is often used for outsourced portions of a project, repetitive work within a project, or a subproject.

AKA subnet

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

Free float

A

Total time activity can be delayed without affecting early start of its immediately successor activities.

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

Hard logic

A

Logic that described activities that must happen in a particular order.

e.g. excavate before foundation.

aka mandatory dependancy.

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

Internal dependencies

A

Internal relationships to the project or organization.

e.g. project team must create the software as part of hte project’s deliverable before software can be tested for quality control.

20
Q

Lag time

A

Positive time that moves two or more activities further apart.

Waiting time between activities.

21
Q

Late Finish (LF)

A

The latest a project activity can finish.

Used in backward pass procedure to discover the critical path and projcet float.

22
Q

Lead time

A

Negative time. Brings two activities closer together (or overlaps).

Also thought of as an acceleration of the successor activity (only possible on finish-startl).

23
Q

Management Reserve

A

A percentage of the project duration to combat parkinson’s law (work expands to time allotted).

When project activities become late, there lateness is subtracted from the management reserve.

24
Q

Mandatory dependencies

A

These dependencies are the natural order of activities (e.g. foundation before house).

AKA hard logic.

25
Q

Monte Carlo analysis

A

Project simulation approach that predicts how all scenarios will play out. Gives a range of possible answers (like a histogram)

26
Q

Parametric analysis

A

Quantitatively based duration estimate that uses formulas to determine how long activity will take based on quantities of work to be completed.

27
Q

Parkinsons law

A

Work expands to fill allotted time.

28
Q

Planning package

A

WBS entry located below control account and above work package.

Signifies that there is more planning that needs to be completed for this specific deliverable

29
Q

Precedence diagramming method

A

Network diagram that shows activities in nodes and the relationships between each activity.

30
Q

Project calendars

A

Calendars that identify when the project work will occur.

31
Q

Project float

A

Total time a project can be delayed without delaying customer-expected due date

32
Q

Project network diagram

A

Diagram that visualizes the flow of project activities and relationship to other activities

33
Q

Refinement

A

Update to the WBS

34
Q

Resource Breakdown Structure (RBS)

A

Hierarchal breakdown of project resources by category and resource type.

e.g. category for equip, human resources, materials - each with diff types.

35
Q

Resource Calendars

A

Calendars that identify when project resources are available for project work.

36
Q

Resource-leveling heuristic

A

Method to flatten the schedule when resources are overallocated.

e.g. to ensure workers are not overextended on activities.

37
Q

Rolling wave planning

A

The imminent work is planned in detail, while the future work is planned at a high level.

Form of progressive elaboration.

38
Q

Schedule management plan

A

Subsidiary PM plan.

Defines how scheudle will be created, estimated, controlled, and managed.

39
Q

Soft logic

A

Activities don’t necessarily have to happen in a specific order.

PM could use soft logic to change order if so ddesired.

40
Q

Start to Finish

A

Activity relationship. One activity needs to start so that it’s successor can finish.

Very unusual.

41
Q

Start to start

A

Activity relationship that requires current activity to start before successor can start.

42
Q

Subnet

A

Representation of project network diagram that is often used for outsourced portions of the projects, repetitive work with a projcet, or a subproject.

Also called fragnet.

43
Q

Template

A

Prepopulated component.

44
Q

Three-point estimate

A

Estimating technique that requires optimistic, most likely, and pessimistic estimate to be created.

Three estimates are averaged.

PERT is the one where the most likely is weighted higher.

45
Q

Total float

A

Total time an activity can be delayed without delaying project completion

46
Q

work package

A

Smallest item on the work breakdown structure.