liveBook · Manning

Expected activity time

As explained in Statistics Every Programmer Needs

Activity duration is the expected amount of time required to complete a project activity.

Expected activity time is the duration assigned to a project activity after combining three estimates: optimistic time, most likely time, and pessimistic time. PERT uses their weighted average when detailed historical information is unavailable, supporting project forecasting and scheduling. section 13.2

Estimate an activity’s duration by:

  • Collecting an optimistic time, assuming unusually favorable conditions. section 13.2
  • Collecting a pessimistic time, assuming unusually unfavorable conditions. section 13.2
  • Collecting the most likely time under normal conditions. section 13.2
  • Calculating the PERT weighted average and assigning only the resulting expected time to the activity. section 13.2
  • Using the resulting durations in forward and backward passes to calculate earliest and latest schedule times and identify the critical path. section 13.3 section 13.3.1

Automated reporting tool

For Activity A, the optimistic estimate is 2 weeks, the most likely estimate is 3 weeks, and the pessimistic estimate is 4 weeks. The resulting expected activity time is 3 weeks, which becomes the duration assigned to Activity A. Across all listed activities, expected times sum to 39 weeks, but parallel work means this is not the project duration; the network analysis gives a 29-week timeline. section 13.2 section 13.3.1

Figure 13.1 An illustration of the beta probability distribution assumed by PERT that displays the optimistic, pessimistic, and most likely activity times. The area under the curve represents the probability of different completion times, with the peak indicating the most likely duration.
figure

Visualizes the beta probability distribution assumed by PERT, including optimistic, most likely, and pessimistic times and the probability area between them. section 13.2

How Statistics Every Programmer Needs covers it

How deep it goes
Defines three inputs, weighted averaging, assumptions, and schedule use, but does not detail the complete statistical derivation.
Examples
Uses Activity A estimates of 2, 3, and 4 weeks, a 39-week activity total, and a 29-week dependency-network timeline.
What it assumes
Assumes activity definitions, expert judgment, and task dependencies while teaching the three-point estimation process.
What you can do after
Apply it via PERT to assign activity durations and support critical-path scheduling and deadline decisions.
How it connects
Connects PERT with project scheduling, dependencies, critical path, forward pass, and project crashing.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Statistics Every Programmer Needs. The section links point to the parts of the book it draws on.