The Earned Schedule Exchange


January 27, 2022
Project Recovery and To Complete Schedule Performance Index

Concept: You know that things aren’t going well. Tempers are flaring at Zoom sessions. Sick calls are coming in, even though everyone’s been isolating. Costs are building faster than expected, and several deliverables are running late. But, how bad is it?

If action is needed, it’s better taken early than late, but if you’re wrong, you’ll lose credibility. So, what do you do?

Get the facts...from Earned Schedule.

Recovery_Man_w_Wrench.png

Practice: Sound principles and proven math turn your schedule into metrics that help you decide.

TSPI in Concept

One such metric is the To Complete Schedule Performance Index (TSPI).

TSPI is a prescriptive metric. It prescribes the future performance level needed to achieve the desired duration.

TSPI is a ratio between two differences: the difference between planned duration and earned schedule and the difference between total duration and actual time.

In the context of the plan, total duration is given by the Planned Duration, and the formula is (PD – ES) / (PD – AT). In the context of estimates, total duration is given by the Estimated Duration, and the formula is (PD – ES) / (ED – AT).

Planned Duration is derived directly from the baseline schedule. It is the difference between the baseline finish date and baseline start date. Estimated Duration can be based on statistical analysis of past performance or on analysis of risks, opportunities, and external factors.

TSPI can be used to assess the feasibility of the planned or estimated duration. For this purpose, TSPI is compared to a specific threshold value, namely, 1.10.

1.10_Threshold_3.png

If TSPI is steadily below the threshold or falling away from it, recovery is not called for. As TSPI climbs toward the threshold, the need for action rises. Once the threshold is breached, the duration can be regarded as unrecoverable.

TSPI in Action

TSPI can be represented in a chart. Add the 1.10 threshold to make trends easy to see.

In the chart, the vertical axis represents the index value. It can start at 0 and increase to the maximum observed value or to the threshold value, whichever is greater.

The horizontal axis is set at the estimated duration. Note that the estimated completion date can be used in place of numerical periods—simply add duration estimates to the starting date.

The recoverability threshold   is represented as a straight line at 1.10. The line extends from the first period to the last period.

TSPI is then represented as a series of values between zero (0) and the maximum value. The line expressing TSPI extends from the first period in which value is earned to the actual time.

Note that the maximum and minimum values of the index can be adjusted up or down to improve the appearance of the chart, as shown in Figure 1.

TSPI_large_in_figma_v1.png

Figure 1

In Figure 1, recovery is not indicated over the first three months, as TSPI is below the threshold and is essentially flat.

Over the next three months, the TSPI rises steadily toward the threshold value. That’s a call to action: recover or else.

In the example, action is taken. Problems are identified. Root-cause analysis is done. Remediation is planned and initiated.

While those steps are underway, TSPI hovers just below the threshold value. During that period, it is unclear whether or not remediation is successful. But, at least, the situation is not worsening.

Finally, the last three months show that remediation is effective, and recovery is in hand.

From this point forward, TSPI can be monitored to ensure an on-time finish.

Bonus Topic: Trend Analysis

From one time period to the next, there is natural variance in schedule performance. If that variance happens to cross a threshold value, it can signal a need for action. Although you can take action immediately, you run the risk of an unnecessary escalation. Too many of them and the call to action loses its strength.

Trend analysis is one way to avoid unnecessary escalations. Rather than respond immediately to an individual threshold breach, you determine if the breach is part of a trend and then determine if action is called for.

Trend analysis is especially important for TSPI. If you wait until TSPI breaches the 1.10 threshold, it is too late to respond effectively. You need to take action long before that point is reached.

Trends comprise three or more consecutive measurements. For TSPI, if the consecutive measurements converge on the threshold value of 1.10, take action. If the trend is away from the 1.10 threshold, you can stand down. Otherwise…

TSPI sometimes hovers just under the 1.10 threshold. Proximity to the threshold suggests the need for escalation, but it also leaves open the possibility of an on-time finish.

In such cases, other recovery measurements can help decide the matter: the window of opportunity for recovery, performance level required in each recovery period, and probability of recovery. All of these metrics will be addressed in future posts.

Summary

The To-complete Schedule Performance Index (TSPI) is a prescription for future schedule efficiency. It prescribes the level of efficiency required to complete the project within a target duration. The target duration may be either the Planned Duration or the Estimated Duration. Keep TSPI below the threshold value of 1.10 to complete the project on time.

Add new comment

All fields are required.

*

*

*

No Comments


January 27, 2022
Path to Failure, Road to Recovery: Earned Schedule and Project Recovery

Concept: What are the sign posts on the path to project failure? They are many and varied. Here are a couple of prominent ones:

  • behavioural  markers such as optimism bias and strategic misrepresentation,
  • quantitative indicators such as cost increase and schedule delay.

Projects have inertia built from early investments in time, money, and political influence. So, it’s difficult to call out the need for recovery and even more difficult to take action. That’s one reason failures happen so often: the time to act has long-since passed.

What is the antidote to hesitation?

    TSPI_Man_Pull_Arrow.png

    Practice: The antidote depends on its root cause.

    Sometimes, hesitation results from uncertainty: were initial estimates inaccurate? Are current measurements of progress wrong? Did somebody make a mistake?

    Other times, hesitation is intentional. Initial estimates were tailored to fit political and organizational expectations. Current measurements are willfully ignored or, worse, distorted. There is no rush to expose deviations.

    Addressing intentional hesitation requires broad political and organizational measures such as contract incentives and regulatory oversight. That’s an important topic, but it lies beyond the scope of my posts. For a reference, click here.

    Where hesitation results from uncertainty, facts matter. Quantitative measurements combat the uncertainty. It’s these situations in which Earned Schedule can help.

    For project recovery, Earned Schedule answers key questions:

    • Is recovery needed? If so, is it time to act?
    • What level of performance is required to recover the target date?
    • What is the window of opportunity for recovery?
    • What level of performance is required in each of the recovery periods?    
    • What is the probability the project will recover?

    For answers, see the next series of posts.

    Add new comment

    All fields are required.

    *

    *

    *

    No Comments


    January 2, 2022
    Blog Topics

    SPIt Thresholds     TSPI, Rx for Success    ES Statistical Analysis  

    Schedule Adherence Concept   P-Factor Calcs   P-Factor Use  Rework and Waste  Calculating Rework

    AgileES HOW-TO's:  1 Estimate Velocity, 2 Baseline the Schedule, 3 Get Data & 4 Calc Metrics,

    5 Assess Performance, 6 Plan Sprints, 7 Re-baseline, 8 Repeat 3-7 and Report Status

    More on Agile: AgileES Rationale  Agile4ES  AgileES Math  ES Burndown  
                                            Agile Statistical Analysis        

         EACt Thresholds                         NDIA Limitations 

      ES Reliability     Project Topology

    Longest Path Intro     Longest Path Calculation     Longest Path Thresholds 

    LP ES(L) Burndown     LP SPIt          LP Tools


    ProjectFlightDeck home page for ES products and services: PFD Home

    Add new comment

    All fields are required.

    *

    *

    *

    No Comments




    Archives