liveBook · Manning

Activity variance

As explained in Statistics Every Programmer Needs

Activity variance is a measure of uncertainty or variability in a project's estimated activity duration.

Activity variance measures uncertainty in an activity’s estimated duration. Using optimistic time a and pessimistic time b, calculate variance as ((b − a) / 6)². Higher values indicate less predictable durations; lower values indicate more consistent estimates. section 13.4

For a project, sum variances only for activities on the critical path, assuming activity times are statistically independent. The square root gives project standard deviation, which supports completion-probability analysis with a normal distribution and z-score. section 13.4

Automated reporting tool

Activity A has optimistic and pessimistic estimates of 2 and 4 weeks, producing variance 1/9. A Python calculation using SciPy combines project mean, standard deviation, and due date to estimate completion probability. section 13.4

How Statistics Every Programmer Needs covers it

How deep it goes
Defines and calculates activity variance, then aggregates critical-path variances under independence assumptions.
Examples
Uses Activity A, an automated reporting tool variance table, and SciPy completion-probability code.
What it assumes
Assumes optimistic and pessimistic duration estimates and introduces standard deviation, normal probability, and z-score use.
What you can do after
Apply the formula, aggregate critical-path variance, and estimate deadline probability with a z-score.
How it connects
Connects activity variance with critical path, project duration, standard deviation, normal probability distribution, and z-score.

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.