Ch 6 - Project Schedule Managment Flashcard (not compelete)

1
Q

The primary output of breaking down the WBS work packages.

A

Activity list

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

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

A

Alternative analysis

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

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

A

Analogous estimating

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

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.

A

Bottom-up estimating

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

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.

A

Control threshold

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

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 this. The specifics of this are documented in this plan.

A

Control account

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

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

A

Crashing

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

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. Activities in the this have no float.

A

Critical path

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

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. These 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.

A

Discretionary dependencies

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

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

A

Early finish

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

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

A

Early start

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

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.

A

External dependencies

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

A schedule compression method that changes the relationship of activities. With this, activities that would normally be done in sequence are allowed to be done in parallel or with some overlap. This 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, this does add risk to the project.

A

Fast tracking

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

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

A

Finish-to-finish

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

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

A

Finish-to-start

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

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.

A

Fragnet

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

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

A

Free float

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

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.

A

Hard logic

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

The process of establishing policies, procedures, and documentation for planning, developing, managing, executing, and controlling the project schedule.

A

Plan Schedule Management

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

A detailed, hierarchical breakdown of the project scope, deliverables, and tasks into manageable sections.

A

Work Breakdown Structure (WBS)

21
Q

A technique that involves estimating the duration of individual activities by using the activity’s scope and resources.

A

Bottom-up Estimating

22
Q

The process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule model.

A

Develop Schedule

23
Q

A technique that allows the project to continue without disrupting the critical path by increasing resources or working overtime.

A

Crashing

24
Q

The process of identifying and documenting the specific actions to be performed to produce the project deliverables.

A

Define Activities

25
Q

The method used to graphically represent the sequence, duration, and dependencies of project activities.

A

Network Diagram

26
Q

A type of dependency in project scheduling that is contractually or legally required.

A

External Dependency

27
Q

A sequence of activities that represents the longest path through a project, which determines the shortest possible project duration.

A

Critical Path

28
Q

A schedule format where activities are listed in a sequence, along with their estimated durations, start, and finish dates.

A

Gantt Chart

29
Q

A graphical representation that shows the interdependencies among activities in a project schedule.

A

Precedence Diagramming Method (PDM)

30
Q

The process of determining the type and quantity of resources needed to complete project activities.

A

Estimate Activity Resources

31
Q

A technique used to calculate the early start, early finish, late start, and late finish dates for each activity in the project schedule model.

A

Critical Path Method (CPM)

32
Q

The process of monitoring the status of the project to update the project schedule and manage changes to the schedule baseline.

A

Control Schedule

33
Q

A type of dependency that is inherent in the nature of the work being done and often involves physical limitations.

A

Mandatory Dependency

34
Q

A method of adjusting start and finish dates based on resource availability, often used when resources are limited.

A

Resource Leveling

35
Q

The technique of adding buffer time between tasks to manage uncertainty and reduce the risk of schedule delays.

A

Padding

36
Q

A schedule network analysis technique that takes into account both the longest path (critical path) and resource constraints.

A

Critical Chain Method

37
Q

The process of allocating resources to project activities to achieve the best schedule performance while minimizing costs and risks.

A

Resource Optimization

38
Q

The process of estimating the number of work periods needed to complete individual activities with estimated resources.

A

Estimate Activity Durations

39
Q

A visual representation of the work remaining for the project, usually in the form of a bar or line chart.

A

Work Breakdown Structure (WBS) Dictionary

40
Q

The process of identifying and documenting relationships among the project activities.

A

Sequence Activities

41
Q

The factor that prevents an activity from starting or finishing until a preceding activity is complete.

A

Predecessor Activity

42
Q

The point in time when a deliverable is due or a project milestone is reached.

A

Milestone

43
Q

The schedule development method that calculates a range of possible project completion dates by applying three-point estimates (optimistic, pessimistic, and most likely).

A

Program Evaluation and Review Technique (PERT)

44
Q

The difference between the early and late start or finish times of a task in the project schedule, indicating the amount of time a task can be delayed without affecting the project finish date.

A

Float (or Slack)

45
Q

The technique that allows for the project schedule to be adjusted based on the availability of resources, potentially delaying tasks without impacting the project’s completion date.

A

Resource Smoothing

46
Q

The technique used to determine the feasibility of the project schedule and identify where adjustments might be needed.

A

Schedule Network Analysis

47
Q

A practice where some activities are overlapped to shorten the project duration, but this could increase risk and costs.

A

Fast Tracking

48
Q

A delay in the start of a successor activity to account for time required by a predecessor activity.

A

Lag Time