6 Schedule Management Terms Flashcards

1
Q

Activity list

A

The 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

The identification of more than one
solution. Consider roles, materials, tools,
and approaches to the project work.

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

Analogous estimating

A

A somewhat unreliable estimating
approach that relies on historical
information to predict what current activity
durations should be. Analogous
estimating is more reliable, however, than
team member recollections. Analogous
estimating is also known as top-down
estimating and is a form of expert
judgment.

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

Bottom-up estimating

A

The most accurate time-and-cost
estimating approach a project manager
can use. This estimating approach starts
at “the bottom” of the project and
considers every activity, its predecessor
and successor activities, and the exact
amount of resources needed to complete
each activity.

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

Control account

A

A WBS entry that considers the time,
cost, and scope measurements for that
deliverable within the WBS. The
estimated performance is compared
against the actual performance to
measure overall performance for the
deliverables within that control account.
The specifics of a control account are
documented in a control account plan.

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

Control threshold

A

A predetermined range of acceptable
variances, such as +/–10 percent off
schedule. Should the variance exceed
the threshold, then project control
processes and corrected actions will be
enacted.

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

Crashing

A

A schedule compression approach that
adds more resources to activities on the
critical path to complete the project
earlier. When crashing a project, costs
are added because the associated labor
and sometimes resources (such as faster
equipment) cause costs to increase.

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

Critical path

A

The path in the project network diagram
that cannot be delayed, otherwise the
project completion date will be late. There
can be more than one critical path.
Activities in the 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

These dependencies are the preferred
order of activities. Project managers
should use these relationships at their
discretion and should document the logic
behind the decision. Discretionary
dependencies allow activities to happen
in a preferred order because of best
practices, conditions unique to the project
work, or external events. Also known as
preferential or soft logic.

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

Early finish

A

The earliest a project activity can finish.
Used in the forward pass procedure to
discover the critical path and the project
float.

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

Early start

A

The earliest a project activity can begin.
Used in the forward pass procedure to
discover the critical path and the project
float.

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

External dependencies

A

As the name implies, these are
dependencies outside of the project’s
control. Examples include the delivery of
equipment from a vendor, the deliverable
of another project, or the decision of a
committee, lawsuit, or expected new law.

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 the relationship of activities.
With fast tracking, activities that would
normally be done in sequence are
allowed to be done in parallel or with
some overlap. Fast tracking can be
accomplished by changing the relation of
activities from FS to SS or even FF or by
adding lead time to downstream
activities. However, fast tracking does
add risk to the project.

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

Finish-to-finish

A

An activity relationship type that requires
the current activity to be finished before
its successor can finish.

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

Finish-to-start

A

An activity relationship type that requires
the current activity to be finished before
its successor can start.

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

Fragnet

A

A representation of a project network
diagram that is often used for outsourced
portions of a project, repetitive work
within a project, or a subproject. Also
called a subnet.

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

Free float

A

This is the total time a single activity can
be delayed without affecting the early
start of its immediately following
successor activities.

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

Hard logic

A

Logic that describes activities that must
happen in a particular order. For
example, the dirt must be excavated
before the foundation can be built. The
foundation must be in place before the
framing can begin. Also known as a
mandatory dependency.

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 the
organization. For example, the project
team must create the software as part of
the project’s deliverable before the
software can be tested for quality control.

20
Q

Lag time

A

Positive time that moves two or more
activities further apart.

21
Q

Late finish

A

The latest a project activity can finish.
Used in the backward pass procedure to
discover the critical path and the project
float.

22
Q

Late start

A

The latest a project activity can begin.
Used in the backward pass procedure to
discover the critical path and the project
float.

23
Q

Lead time

A

Negative time that allows two or more
activities to overlap where ordinarily
these activities would be sequential.

24
Q

Management reserve

A

A percentage of the project duration to
combat Parkinson’s Law. When project
activities become late, their lateness is
subtracted from the management
reserve.

25
Mandatory dependencies
These dependencies are the natural order of activities. For example, you can’t begin building your house until your foundation is in place. These relationships are called hard logic.
26
Monte Carlo analysis
A project simulation approach named after the world-famous gambling district in Monaco. This predicts how scenarios may work out, given any number of variables. The process doesn’t actually churn out a specific answer, but a range of possible answers. When Monte Carlo analysis is applied to a schedule, it can examine, for example, the optimistic completion date, the pessimistic completion date, and the most likely completion date for each activity in the project and then predict a mean for the project schedule.
27
Parametric estimate
A quantitatively based duration estimate that uses mathematical formulas to predict how long an activity will take based on the quantities of work to be completed.
28
Parkinson’s Law
A theory that states: “Work expands so as to fill the time available for its completion.” It is considered with time estimating, because bloated or padded activity estimates will fill the amount of time allotted to the activity.
29
Planning package
A WBS entry located below a control account and above the work packages. A planning package signifies that there is more planning that needs to be completed for this specific deliverable.
30
Precedence diagramming method
A network diagram that shows activities in nodes and the relationship between each activity. Predecessors come before the current activity, and successors come after the current activity.
31
Project calendars
Calendars that identify when the project work will occur.
32
Project float
This is the total time the project can be delayed without passing the customer expected completion date.
33
Project network diagram
A diagram that visualizes the flow of the project activities and their relationships to other project activities.
34
Refinement
An update to the work breakdown structure.
35
Resource breakdown structure (RBS)
This is a hierarchical breakdown of the project resources by category and resource type. For example, you could have a category of equipment, a category of human resources, and a category of materials. Within each category, you could identify the types of equipment your project will use, the types of human resources, and the types of materials.
36
Resource calendars
Calendars that identify when project resources are available for the project work.
37
Resource-leveling heuristic
A method to flatten the schedule when resources are overallocated. Resource leveling can be applied using different methods to accomplish different goals. One of the most common methods is to ensure that workers are not overextended on activities.
38
Rolling wave planning
The imminent work is planned in detail, while the work in the future is planned at a high level. This is a form of progressive elaboration.
39
Schedule management plan
A subsidiary plan in the project management plan. It defines how the project schedule will be created, estimated, controlled, and managed.
40
Soft logic
The activities don’t necessarily have to happen in a specific order. For example, you could install the light fixtures first, then the carpet, and then paint the room. The project manager could use soft logic to change the order of the activities if so desired.
41
Start-to-finish
An activity relationship that requires an activity to start so that its successor can finish. This is the most unusual of all the activity relationship types.
42
Start-to-start
An activity relationship type that requires the current activity to start before its successor can start.
43
Subnet
A representation of a project network diagram that is often used for outsourced portions of projects, repetitive work within a project, or a subproject. Also called a fragnet.
44
Template
A previous project that can be adapted for the current project and forms that are pre-populated with organizational-specific information.
45
Three-point estimate
An estimating technique for each activity that requires optimistic, most likely, and pessimistic estimates to be created. Based on these three estimates, an average can be created to predict how long the activity should take.
46
Total float
This is the total time an activity can be delayed without delaying project completion.
47
Work package
The smallest item in the work breakdown structure.