Chapter 6 - Project Schedule Management 9% Flashcards

1
Q

The process of establishing the 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
2
Q

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

A

Define Activities

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

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

A

Sequence Activities

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

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

A

Estimate Activity Durations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
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

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

This is a form of rolling wave planning based on adaptive life cycles, such as the agile approach for product development. The requirements are documented in user stories that are then prioritized and refined just prior to construction, and the product features are developed using time-boxed periods of work. This approach is often used to deliver incremental value to the customer or when multiple teams can concurrently develop a large number of features that have few interconnected dependencies.

A

Iterative Scheduling with a Backlog

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

This approach, typically used in a Kanban system, is based on the theory-of-constraints and pull-based scheduling concepts from lean manufacturing to limit a team’s work in progress in order to balance demand against the team’s delivery throughout. This does not rely on a schedule that was developed previously for the development of the product or product increments, but rather pulls work from a backlog or intermediate queue of work to be done immediately as resources become available.

A

On-Demand Scheduling

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

A component of the project management plans that describes how the project costs will be planned, structured, and controlled. It can establish the following:

  • Units of measure: Each unit used in measurement is defined for each of the resources.
  • Level of precision: The degree to which cost estimates will be rounded up/down (995.59 to 1000) based on the scope of the activities and magnitude of the project.
  • Level of accuracy: The acceptable rant (+/-10%) used in determining realistic cost estimates is specified, and may include an amount for contingencies.
A

Cost Management Plan

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

A technique used for constructing a schedule model in which activities are represented by nodes and are geographically linked by one or more logical relationships to show the sequence in which the activities are to be performed. Consists of four types of dependencies or logical relationships:

  1. Finish-to-Start (FS)
  2. Finish-to Finish (FF)
  3. Start-to-Start (SS)
  4. Start-to-Finish (SF)
A

Precedence Diagramming Method (PDM)

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

A logical relationship in which a successor activity cannot start until a predecessor activity has finished.

A

Finish-to-Start (FS)

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

A logical relationship in which a successor activity cannot finish until a predecessor activity has finished.

A

Finish-to Finish (FF)

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

A logical relationship in which a successor activity cannot start until a predecessor activity has started.

A

Start-to-Start (SS)

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

A logical relationship in which a predecessor activity cannot finish until a successor activity has started.

A

Start-to-Finish (SF)

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

Legally or contractually required or inherent in the nature of the work. Sometimes referred to as hard logic or hard dependencies.

A

Mandatory Dependencies

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

Established based on knowledge of best practices within a particular application area or some unusual aspect of the project where a specific sequence is desired, even though there may be other acceptable sequences. Sometimes referred to as preferred logic, preferential logic, or soft logic.

A

Discretionary Dependencies

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

Involve a relationship between project activities and non-project activities (usually outside of the project team’s control).

A

External Dependencies

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

Involve a precedence relationship between project activities and are generally inside the project team’s control.

A

Internal Dependencies

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

The amount of time a successor activity can be advanced with respect to a predecessor activity. Often represented as a negative value for lag in scheduling software.

A

Lead

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

The amount of time a successor activity will be delayed with respect to a predecessor activity.

A

Lag

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

A graphical representation of the logical relationships, also referred to as dependencies, among the project schedule activities.

A

Project Schedule Network Diagram

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

A technique for estimating the duration or cost of an activity or a project using historical data from a similar activity or project.

A

Analogous Estimating

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

A technique for estimating in which an algorithm is used to calculate cost or duration based on historical data and project parameters.

A

Parametric Estimating

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

This estimate is based on the duration of the activity, given the resources likely to be assigned, their productivity, realistic expectations of availability for the activity, dependencies on other participants, and interruptions.

A

Most Likely (tM)

24
Q

The activity duration based on analysis of the best-case scenario for the activity.

A

Optimistic (tO)

25
Q

The duration based on analysis of the worst-case scenario for the activity

A

Pessimistic (tP)

26
Q

The average of the three-points of estimating.

A

Expected Duration (tE)

27
Q

Triangular Distribution Formula; used when there is insufficient historical data or when using judgmental data.

A

tE = (tO + tM + tP) / 3

28
Q

Method of estimating project duration or cost by aggregating the estimates of the lower-level components of the WBS. Work can be decomposed into more detail if an accurate estimate can’t be determined.

A

Bottom-Up Estimating

29
Q

Used to determine the amount of contingency and management reserve needed for the project. Duration estimates may include contingency reserves, sometimes referred to as schedule reserves, to account for schedule uncertainty.

A

Reserve Analysis

30
Q

The estimated duration within the schedule baseline, which is allocated for identified risks that are accepted. Associated with the known-unknowns which may be estimated to account for this unknown amount of rework. May be a percentage of the estimated activity duration or a fixed number of work periods. May be separated from individual activities and aggregated as more precise info about the project becomes available, this may be used, reduced, or eliminated. It should be clearly identified in the schedule documentation.

A

Contingency Reserves

31
Q

A specified amount of the project budget withheld for management control purposes and are reserved for unforeseen work that is within scope of the project. Intended to address the unknown-unknowns that can affect a project. It is not included in the schedule baseline, but it is part of the overall project duration requirements. Depending on contract terms, use of it may require a change to the schedule baseline.

A

Management Reserves

32
Q

Voting technique often used in agile-based projects where team is asked to show support for a decision by holding up their hand. A closed fist = 0. If less than 3 fingers are held up, the team member is given the opportunity to discuss any objects with the team. Continues until a consensus is achieved (all members with at least 3 fingers up) or the team agrees to move onto the next decision.

A

Fist of Five / Fist to Five

33
Q

Quantitative assessments of the likely number of time periods that are required to complete an activity, a phase, or a project. Do not include any lag time. May include some indication of a range of possible results.

A

Duration Estimates

34
Q

Extend the description of the activity by identifying multiple components associated with each activity. The components evolve over time. During the initial stages, they include the unique activity identifier (ID), WBS ID, and activity label or name. Can be used to identify where the work has to be performed, the project calendar the activity is assigned to, and the type of effort involved. Used for schedule development and for selecting, ordering, and sorting the planned schedule activities in various ways within the report.

A

Activity Attributes

35
Q

The process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create a schedule model for project execution and monitoring and controlling. IT generates a schedule model with planned dates for completing project activities. Performed throughout the project.

A

Develop Schedule

36
Q

The overarching technique used to generate the project schedule model. It employs several other techniques such as critical path method, resource optimization techniques, and modeling techniques. Iterative process that is employed until a viable schedule model is developed.

A

Schedule Network Analysis

37
Q

Used to estimate the minimum project duration and determine the amount of schedule flexibility on the logical network paths within the schedule model. It calculates the early start, early finish, late start, and late finish dates for all activities without regard for any resource limitations by performing a forward and backward pass analysis through the schedule network.

Also used to calculate the amount of total and free float or schedule flexibility on the logical network paths within the schedule model.

A

Critical Path Method

38
Q

The amount of time that a schedule activity can be delayed without delaying the early start date of any successor or violating a schedule constraint.

A

Free Float (float also called slack)

39
Q

The amount of time that a schedule activity can be delayed or extended from its early start date without delaying the project finish date or violating a schedule constraint.

A

Total Float (float also called slack)

40
Q

Caused when a backward pass is calculated from a schedule constraint that is later than the early finish date that has been calculated during forward pass calculation.

A

Positive Total Float

41
Q

Caused when a constraint on the late dates is violated by duration and logic.

A

Negative Total Float

42
Q

A technique that helps to find possible accelerated ways of bringing a delayed schedule back on track.

A

Negative Float Analysis

43
Q

A technique in which start and finish dates are adjusted based on resource constraints with the goal of balancing the demand for resources with the available supply. Can be used when shared or critically required resources are available only at certain times or in limited quantities or are over-allocated, such as when a resource has been assigned to 2 or more activities during the same time period or there is a need to keep resource usage at a constant level. Can often cause the original critical path to change.

A

Resource Leveling

44
Q

Models the combined effects of individual project risks and other sources of uncertainty to evaluate their potential impact on achieving project objectives.

A

Simulation

45
Q

Simulation technique in which risks and other sources of uncertainty are used to calculate possible schedule outcomes for the total project.

A

Monte Carlo Analysis

46
Q

The process of evaluating scenarios in order to predict their effect, positive or negative, on project objectives. Can be used to assess the feasibility of the project schedule under different conditions, and in preparing schedule reserves and response plans to address the impact of unexpected situations.

A

What-if Scenario Analysis

47
Q

A schedule compression technique used to shorten the schedule duration for the least incremental cost by adding resources. Examples include approving overtime, bringing in additional resources, or paying to expedite delivery to activities on the critical path. Only works for activities on the critical path where additional resources will shorten the activity’s duration. Does not always produce a viable alternative and may result in increased risk and/or cost.

A

Crashing

48
Q

A schedule compression technique in which activities or phases normally done in sequence are performed in parallel for at least a portion of their duration. It may result in rework and increased risk. It only works when activities can be overlapped to shorten the project duration on the critical path. Using leads in case of schedule acceleration usually increases coordination efforts between the activities concerned and increases quality risk. May also increase project costs.

A

Fast Tracking

49
Q

Provides a high-level summary timeline of the release schedule (typically 3-6 months) based on the product roadmap and the product vision for the product’s evolution. Also determines the number of iterations or sprints in the release, and allows the product owner and team to decides how much needs to be developed and how long it will take to have a releasable product based on business goals, dependencies, and impediments.

A

Agile Release Planning

50
Q

The approved version of a schedule model that can be changed only through formal change control procedures and is used as a basis for comparison to actual results. Used during monitoring and controlling to compare to actual start and finish dates to determine if variances have occurred.

A

Schedule Baseline

51
Q

An output of a schedule model that presents linked activities with planned dates, durations, milestones, and resources. At a minimum, includes a planned start date and planned finish date for each activity. If done early, may remain preliminary until resource assignments have been confirmed and start/finish dates are established.

A

Project Schedule

52
Q

Represents schedule information where activities are listed on the verticle axis, dates are on the horizontal axis, and activity durations are shown as horizontal bars placed according to start and finish. Float can be depicted or not.

A

Bar Chart / Gantt Chart

53
Q

Represents schedule information where major deliberables and key external interfaces are listed on the verticle axis, dates are on the horizontal axis, and activity durations are shown as horizontal bars placed according to start and finish. Float can be depicted or not.

A

Milestone Chart

54
Q

The collection of information for decribing and controlling the schedule for the project schedule model.

Includes at a minimum, schedule milestones, activities, activity attributes, and documentation of all identified assumptions and constraints.

A

Schedule Data

55
Q

Tracks the work that remains to be completed in the iteration backlog. Used to analyze the variance with respect to an ideal burndown based on the work committed from iteration planning.

A

Iteration Burndown Chart

56
Q

Measures, compares, and analyzes schedule performance against the schedule baseline such as actual start and finish dates, percent complete, and remaining duration for work in progress.

A

Performance Review

57
Q

A technique that adjusts the activities of a schedule model such that the requirements for resources on the project do not exceed certain predefined resource limits. The project’s critical path is not changes and the completion date may not be delayed. (activities may only be delayed within their free and total float). May not be able to optimize all resources.

A

Resource Smoothing