Predictive controls and plan diagnosis

Concept and mechanism

A predictive approach can be useful when outcomes and interfaces are stable enough to prepare commitments, sequence work and compare execution with an approved reference. This does not mean nothing can change. Changes need impact assessment, authority and traceability.

Team location does not by itself determine the life cycle: a distributed team can work from a stable design while tailoring communication and coordination. In a matrix, confirm capacity with whoever controls specialists. Scope approval does not automatically reserve people.

Also distinguish phases from management activities. A construction phase may include detailed planning, execution and control at the same time. Waiting until the end to measure variance removes correction opportunities.

Use templates and earlier experience as a starting point, tailoring criteria, responsibilities and current customer obligations. Forecasts may change as information improves; the baseline changes only through the applicable decision process.

Presenting both figures separately makes it possible to distinguish variance, an approved change and merely an updated estimate.

Guided application

The WBS decomposes scope into components and work packages; the schedule describes activities, dependencies and dates. A package may need several activities. Its WBS dictionary should make inclusions, exclusions, outcome and relevant criteria understandable.

Do not omit training, management, testing or documentation included in approved work merely because they are not visible features. A six-month package that prevents assigning or observing progress may need further decomposition. Detail reaching minute-long actions without management value may be excessive.

Seek a level supporting estimation, assignment and control. When a future phase depends on a study, detail near-term work and retain future planning at the level supported by available information. This does not authorize adding scope without a decision.

For quality, connect each requirement to a measure and observation conditions. If 95% of responses must arrive below two seconds at a defined load, an isolated mean does not establish compliance. Fixing a defect also does not prove that the criterion passed: post-change verification remains necessary.

Technical results can support acceptance but do not replace contractually defined acceptance authority.

Read the network and capacity

In this lesson’s simple examples, links are finish-to-start, the calendar is shared and no dates are imposed unless stated otherwise. An activity with two predecessors waits for the later one. The longest-duration path determines completion under these conditions.

Calculate total float as late start minus early start, or late finish minus early finish. Free float indicates how far an activity can slip without delaying its successor’s early start. Confuse neither with available resources.

If two activities require the same person full time, the logical network may show parallelism that cannot be executed. Different calendars, holidays and availability can also change dates. Represent review duration before the milestone marking its completion; a milestone does not perform work.

When shortening an activity, recalculate relevant paths: another may become the finish constraint. Overlapping previously sequential work may increase rework. Adding resources or accelerating may cost more and helps overall timing only if it affects the limiting sequence.

Negative float against a mandatory date calls for data validation and a recovery or renegotiation decision; deleting the constraint does not fulfil the commitment.

Earned value and forecast assumptions

PV is the budgeted value of work planned by the status date; EV is the budgeted value of work recognized as performed under the defined rule; AC is corresponding actual cost. Use the same scope and status date. One rule may recognize value only at acceptance; another may assign credit at start and finish.

Apply the agreed rule rather than changing it after observing results. CV=EV−AC and SV=EV−PV. CPI=EV/AC and SPI=EV/PV, where denominators permit calculation.

CPI below one means less budgeted value obtained per unit of cost; it does not measure project percent complete. SPI describes work value against plan and needs to be read alongside the network. At late completion of all scope, EV and PV may match and SV may be zero despite actual delay.

To forecast cost, state the assumption: EAC=BAC/CPI extends observed efficiency; EAC=AC+(BAC−EV) assumes remaining work at budgeted cost; a new remaining estimate gives EAC=AC+ETC. These are conditional models, not interchangeable answers. VAC=BAC−EAC compares budget and final forecast.

A monthly improvement does not erase earlier costs: calculate cumulative indices from totals rather than averaging monthly indices with different volumes.

Artifacts supporting decisions

A control report should identify baseline version, data status date, current result, forecast and actions. The change log connects request, impact, authorization and implementation; the issue log tracks events already requiring handling. If an approved change creates v3, testing v2 does not establish v3 compliance.

Confirm the authorized reference and route correction or deviation to the appropriate authority. When a new baseline is approved, retain reconciliation with the previous one to distinguish change effects from earlier variance. For cost, a late invoice can make payment differ from cost incurred in the period; apply accounting rules and identify unreconciled amounts.

For progress, identical percentages may represent different things, such as hours spent and accepted units. Before aggregating, check denominators, weights and criteria. Useful control makes the required decision and supporting evidence explicit.

From inspection to the delivery decision

Consider a delivery whose approved version exports data with currency identification. The supplier implemented the earlier version, which omits that field. Old tests passed because they never checked it.

The test pass rate can be one hundred percent without proving compliance with the current commitment. First confirm the authorized version and the connection between requirement, test and result. Then record the difference, consumer impact and options.

Correction may change timing; temporary acceptance may require a customer decision with explicit conditions. The team does not acquire that authority merely because closure is approaching. An approved exception should specify scope, duration and who monitors resolution.

If delivery is corrected, retain earlier evidence and collect the new verification result. This sequence distinguishes defect discovery, corrective action, verification and acceptance. A single green task-board status does not communicate all those dimensions.

Common pitfalls

Using the sum of parallel activities as duration; treating float as extra capacity; confusing spent hours with accepted work; comparing cumulative data with one month’s amounts; using monetary SV as days; assuming tests of one version validate another; replacing the baseline with a forecast without approval.