In a master schedule, an activity is called a summary activity if it has sub activities under it. Any activity having no sub-activity is called a Leaf Activity.

The progress of a summary activity is computed based on the progress of its leaf activities. Lean PlanDo does not consider duration of summary activities to calculate progress for any summary activity (even if a summary has child activities which are again summary, it does not consider their duration to calculate progress). For every activity, all the lowest level leaf activities are obtained and then their duration are considered for progress calculation.

There are 2 types of progress in Lean PlanDo: Planned and Actual. Planned progress at a point of time is the amount of work that needs to be finished according to the baseline schedules (base dates). Actual progress is the progress accumulated through the actual progress updated on the tasks under leaf activities that are planned out in the project.

The calculation method of these two progress types is explained as follow.
​

Example:

For an activity A with base duration of 10 days, planned progress of A at 4th day is:

(4/10) x 100% = 40%

For any summary activity, planned progress at any PoT is calculated from its leaf activities. Base duration of leaf activities are used as their weightage.

Task progress is directly input by users, in terms of percentage or quantity (which will be converted into equivalent percentage). For example:

Actual Progress of Task 1 = 50% (% input by user)

Actual Progress of Task 2 = 8/18 * 100 = 44.40% (8 units input by user)
​

The actual progress of a leaf activity is computed based on the progress of the tasks which has been planned out within the planned portion. See below for two types of activities; fully planned and partially planned.

In this case, Planned Duration is the same as the whole activity duration.
​

In this case, only the first portion of the activity is planned out at the task level. Therefore, Planned Duration of Activity is equal to that particular duration; from the start of Task 1 to the end of Task 2.

Task duration are used as their weightage over the planned portion of the activity.

On deletion of task or activity, percentages are recomputed using the same formula.

Example:

Fully Planned Activity

Example:

Partially Planned Activity

Example:

Expected progress is calculated based on the expected dates of the activities in the project.

The formula is not very different from how we calculate actual progress.

For a leaf activity:

Expected Duration = Base Duration x (Expected Progress)

Expected Progress is derived as below:

We derive the expected progress of an activity relative to a date (in this case do-week end date).

If an activity has expected end date before the do-week end date - then its percentage is derived as 100.

If an activity has expected start date after the do-week end date - then its percentage is derived as 0.

If an activity has expected start date before do-week end date and expected end date after do-week end date - then its percentage is derived as below:

(Duration between expected start date and do-week end date) / (expected duration of activity)

This expected duration is then summed up for all leaf activities under a summary activity.

The above sum is divided with sum of base duration of all leaf activities under the container.

This value is then derived for the overall summary activity of the project to get the expected progress of the project for a given do-week end date