The Project Time Management questions on the PMP® certification exam focus heavily on the program evaluation and review technique (PERT), the critical path method (CPM), the precedence diagramming method (PDM), and the critical chain method; the differences between these four techniques; and the appropriate circumstances for their use. The exam tests your knowledge of how PERT/CPM networks are constructed, how schedules are computed, what the critical path is, and how networks are used to analyze and solve project scheduling, and resource allocation and leveling issues. There is a good chance that you will be presented with a network diagram that will be the subject of five or more questions. Therefore, detailed knowledge of network scheduling is essential. There also seems to be a focus on fast tracking as a method to accelerate the project schedule. You must know the advantages offered by networks over bar charts and network diagrams. You also should understand the concept of float (or slack) and how it presents challenges and opportunities to project schedulers.
Because a thorough understanding of networks and scheduling is required to successfully answer questions on Project Time Management, you should take a course relating to that topic. If you cannot take a course, you may want to consult the user’s manual for one of the more popular desktop software project management packages. Typically, you will find plenty of illustrations and short, easy-to-understand scheduling exercises at the level of detail required to correctly answer the exam questions. Another useful reference is PMI®’s Practice Exam for Scheduling—Second Edition (2011).
The PMBOK® Guide separates the function of Project Time Management into seven processes: plan schedule management, define activities, sequence activities, estimate activity resources, estimate activity durations, develop schedule, and control schedule. Review PMBOK® Guide Figure 6-1 before taking the practice test. Know this chart thoroughly.
Following is a list of the major Project Time Management topics. Use it to help focus your study efforts on the areas most likely to appear on the exam.
Schedule management plan
Define activities
Sequence activities
Estimate activity resources
Estimate activity durations
Develop schedule
Control schedule
INSTRUCTIONS: Note the most suitable answer for each multiple-choice question in the appropriate space on the answer sheet.
Use the following network diagram to answer questions 1 through 4. Activity names and duration are provided.
1. |
a |
b |
c |
d |
2. |
a |
b |
c |
d |
3. |
a |
b |
c |
d |
4. |
a |
b |
c |
d |
5. |
a |
b |
c |
d |
6. |
a |
b |
c |
d |
7. |
a |
b |
c |
d |
8. |
a |
b |
c |
d |
9. |
a |
b |
c |
d |
10. |
a |
b |
c |
d |
11. |
a |
b |
c |
d |
12. |
a |
b |
c |
d |
13. |
a |
b |
c |
d |
14. |
a |
b |
c |
d |
15. |
a |
b |
c |
d |
16. |
a |
b |
c |
d |
17. |
a |
b |
c |
d |
18. |
a |
b |
c |
d |
19. |
a |
b |
c |
d |
20. |
a |
b |
c |
d |
21. |
a |
b |
c |
d |
22. |
a |
b |
c |
d |
23. |
a |
b |
c |
d |
24. |
a |
b |
c |
d |
25. |
a |
b |
c |
d |
26. |
a |
b |
c |
d |
27. |
a |
b |
c |
d |
28. |
a |
b |
c |
d |
29. |
a |
b |
c |
d |
30. |
a |
b |
c |
d |
31. |
a |
b |
c |
d |
32. |
a |
b |
c |
d |
33. |
a |
b |
c |
d |
34. |
a |
b |
c |
d |
35. |
a |
b |
c |
d |
36. |
a |
b |
c |
d |
37. |
a |
b |
c |
d |
38. |
a |
b |
c |
d |
39. |
a |
b |
c |
d |
40. |
a |
b |
c |
d |
The total duration for the path B-C-D-E-I is 15. The duration of any other path in the network is less than 15. [Planning]
Meredith and Mantel 2012, Chapter 8
PMI®, PMBOK® Guide, 2013, 176–177
Meredith and Mantel 2012, Chapter 8
PMI®, PMBOK® Guide, 2013, 176–177
The imposed finish date becomes the late finish for Activity I. The late dates for each activity need to be recalculated. The dates for Activity E become—
Meredith and Mantel 2012, Chapter 8
PMI®, PMBOK® Guide, 2013, 176–177
The late dates for all activities need to be recalculated given the changed duration. Activity G’s revised late dates are—
LF = 11
LS = 6
Meredith and Mantel 2012, Chapter 8
PMI®, PMBOK® Guide, 2013, 176–177
A milestone is a significant point or event in the project. Milestones may be required by the project sponsor, customer, or other external factors for the completion of certain deliverables. They are similar to schedule activities, with the same structure and objectives, but they have zero duration as they represent a moment in time. [Planning]
PMI®, PMBOK® Guide, 2013, 153
For example, in a finish-to-start dependency with a 20-day lag, the successor activity cannot start until 20 days after the predecessor has finished. [Planning]
PMI®, PMBOK® Guide, 2013, 158–159
Three-point estimates are used to determine the estimates that go into the schedule. [Planning and Monitoring and Controlling]
PMI®, PMBOK® Guide, 2013, 170–171, 188–190
Imposed dates on schedule activity starts of finishes can be used to restrict the start of finish to occur either no earlier than a specified date or no later than a specified date. Although all four date constraints typically are available in project management software, “start no earlier than” and “finish no later than” constraints are more commonly used. [Planning]
PMI®, PMBOK® Guide, 2013, 543
The schedule management plan is part of the overall project management plan and defines, among other things, how schedule changes will be managed. Whether it is formal or informal, highly detailed or broadly framed, it generally is based on specific project needs. [Planning]
PMI®, PMBOK® Guide, 2013, 148–149
What-if scenarios (simulation) is a tool and technique for developing schedules by which multiple project durations with different sets of activity assumptions are calculated. Monte Carlo analysis is the most commonly used simulation technique. [Planning]
PMI®, PMBOK® Guide, 2013, 180
E(t)=Optimistic + (4 x Most likely) + Pessimistic6=40 + 200 + 1806=4206= 70 weeks
[Planning]
PMI®, PMBOK® Guide, 2013, 170–171
Fast tracking is a way to accelerate the project schedule. [Planning]
PMI®, PMBOK® Guide, 2013, 181, 190, and 540
The duration of A, which is three, is added to the duration of B, which is four, for a total of seven. The three days between the activities is lag and not duration. The lag is a constraint and must be taken into account as part of the network calculations, but it does not consume resources. The total time by the calendar is 11 days as counted from the morning of Monday the 4th. The lag occurs over Thursday, Friday, and Saturday. Sunday is a nonworkday, so activity B does not start until Monday the 11th. Therefore, the calendar time is 11 days, and activity B ends on Thursday the 14th. [Planning]
PMI®, PMBOK® Guide, 2013, 156, 158–159, and 180
Although limitations exist with all estimating approach, analogous estimating is often used when there is a limited amount of information for the project. It uses historical information and expert judgment. [Planning]
PMI®, PMBOK® Guide, 2013, 169
Mandatory dependencies may be required contractually or be inherent in the nature of the project work. They describe a relationship in which the successor activity cannot be started because of physical constraints until the predecessor activity has been finished. For example, software cannot be tested until it has been developed (or coded). They should not be confused with assigning schedule constraints in the scheduling tool. [Planning]
PMI®, PMBOK® Guide, 2013, 157
The approved project schedule is a key input to schedule control. It is the schedule baseline, as it is the approved version of a schedule model, and it provides the basis for measuring and reporting schedule performance. [Monitoring and Controlling]
PMI®, PMBOK® Guide, 2013, 181,187
While resource leveling will often result in a project duration that is longer than the preliminary schedule as the original critical path probably will change and increase, it can also be used to get a schedule back on track by reassigning activities from noncritical to critical path activities. [Planning]
PMI®, PMBOK® Guide, 2013, 179
First, it is necessary to determine the critical path, which is A, C, F, and G. To determine the lowest weekly crashing cost, start with C at $1,500 per week. The next activity is A, followed by F and G. [Planning]
PMI®, PMBOK® Guide, 2013, 180; Kerzner 2009, 516–519
The completion of the work of the successor activity depends upon the completion of the work of the predecessor activity. [Planning]
PMI®, PMBOK® Guide, 2013, 156
In the create WBS process, final output is described as deliverables or tangible items. In the define activities process, final output is described as activities. [Planning]
PMI®, PMBOK® Guide, 2013, 151
The sequence activity process involves identifying and documenting relationships among the project activities. However, the last activity or milestone are not connected to at least one successor. [Planning]
PMI®, PMBOK® Guide, 2013, 156
The SPI represents how much of the originally scheduled work has been accomplished at a given period in time, thus providing the project team with insight as to whether the project is on schedule. [Monitoring and Controlling]
PMI®, PMBOK® Guide, 2013, 189–190, 224
When identical network descriptions are repeated throughout a project, templates of those activities can be developed. If those series of tasks are repeated several times, the template can be updated several times. Software can be used with the templates to facilitate documenting and adapting them for future use. The sub-network or fragment tends to represent a sub-project or a work package and is often used to illustrate or study some potential or proposed schedule condition, such as a change in preferential schedule logic or the scope of the project. [Planning]
PMI®, PMBOK® Guide, 2013, 564
Slope = (Crash cost – Normal cost)/(Crash time – Normal time). This calculation shows the cost per day of crashing the project. The slope is negative to indicate that as the time required for a project or task decreases, the cost increases. If the costs and times are the same regardless of whether they are crashed or normal, the activity cannot be expedited. [Planning]
Meredith and Mantel 2012, 390; PMI®, PMBOK® Guide, 2013, 181
The scope baseline—made up of the scope statement, WBS, and WBS dictionary—is a key input to the define activities process and are used to develop the activity list that subsequently will help to create the schedule. [Planning]
PMI®, PMBOK® Guide, 2013, 151
Milestones are singular points in time, such as the start or completion of a significant activity or group of activities. [Planning]
PMI®, PMBOK® Guide, 2013, 182
Performance of variance analysis during the schedule monitoring process is a key element of time control. Float variance is an essential planning component for evaluating project time performance. [Monitoring and Controlling]
PMI®, PMBOK® Guide, 2013, 189
Total float or slack is computed by subtracting the early start date from the late start date, or 19 – 10 = 9. To compute the early finish date given a duration of 4, we would start counting the activity on the morning of the 10th; therefore, the activity would be completed at the end of day 13, not 14 (10, 11, 12, 13). If we started the activity on its late start date on the morning of the 19th, we would finish at the end of day 22, not 25. Insufficient information is provided to determine whether this activity can be completed in 2 days if the resources are doubled. [Planning]
Meredith and Mantel 2012, 352–353; PMI®, PMBOK® Guide, 2013, 177
Identifying activity attributes is helpful for further selection and sorting of planned activities. They are used for schedule development and for report formatting purposes. [Planning]
PMI®, PMBOK® Guide, 2013, 153
While there are a number of inputs to define activities, the schedule management plan is a key input. It shows the level of detail necessary to manage the work. [Planning]
PMI®, PMBOK® Guide, 2013, 150
A corrective action is anything that is done to bring expected future schedule performance in line with the schedule baseline. Regarding the project schedule, it usually means taking action to speed up the project. One way to determine why the schedule performance is not in line with the plan is what-if analysis, which may address schedule activities and other scenarios other than the activity that is actually causing the variance. It evaluates scenarios in order to predict their effect on the project’s outcomes, either positive or negative. [Monitoring and Controlling]
PMI®, PMBOK® Guide, 2013, 180, 186
Free float is defined as the amount of time an activity can be delayed without delaying the early start of any immediately succeeding activities. [Planning]
PMI®, PMBOK® Guide, 2013, 177
When using critical chain techniques, the initial project schedule is developed using duration estimates with required dependencies and defined constraints as inputs. [Planning]
PMI®, PMBOK® Guide, 2013, 178
A summary narrative can accompany the schedule network diagram and describe the approach used to sequence the activities in the network. This narrative also should describe any unusual sequences in the network. [Planning]
PMI®, PMBOK® Guide, 2013, 159
The risk register may require updates in both the sequence activities and develop schedule processes. In the sequence activity process, the activity lists and activity attributes may need updates as well. [Planning]
PMI®, PMBOK® Guide, 2013, 160, 185
In estimating activity resources, published estimating data is a tool and technique that is used as many companies routinely publish updated production rates and unit costs of resources. This includes labor trades, material, and equipment for different countries and geographic locations in these countries. [Planning]
PMI®, PMBOK® Guide, 2013, 164
First, compute the standard deviation:
σ=P−O6or36−66=5 days
Next, compute PERT expected time:
P+4(ML)+O6or36+4(21)+66=21days
Finally, determine range of outcomes using 1σ:
21–5 = 16 days, and 21+5 = 26 days
Simply defined, 1σ is the amount on either side of the mean of a normal distribution that will contain approximately 68.26 percent of the population. [Planning]
Meredith and Mantel 2012, 348–350
Project and resource calendars identify periods when work is allowed. Project calendars affect all resources. Resource calendars affect a specific resource or a resource category, such as a labor contract that requires certain workers to work on certain days of the week. [Planning]
PMI®, PMBOK® Guide, 2013, 163, 184, and 558
Duration estimates may include contingency reserves, and contingency should be identified clearly in schedule documentation. They are built into the overall project schedule to account for uncertainty. They also may be developed using quantitative analysis methods. When more information is known about the project, the contingency reserve may be used, reduced, or eliminated. [Planning]
PMI®, PMBOK® Guide, 2013, 171
Because schedule performance index (SPI) and cost performance index (CPI) are expressed as ratios, they can be used to show performance for a specific time period or trends over a long-time horizon. [Monitoring and Controlling]
Kerzner 2009, 650–652
PMI®, PMBOK® Guide, 2013, 190, 219, and 224