Patrick, I don't agree with your statement that "For 99% of the world's projects a schedule update every 2 weeks and a full project update every month is adequate".
In our practice 99% of construction projects are updated at least once in a week, and daily in STO projects.
Project team meetings with performance analysis are usually held weekly and these meetings require updated information on project status and trends for informed decision making. Projects in trouble are updated daily.
In STO time is very expensive and uncertainties can be high. So project is updated each shift.
Member for
24 years 9 months
Member for24 years9 months
Submitted by Vladimir Liberzon on Sun, 2025-04-20 09:26
Patrick, I don't agree with your statement that "For 99% of the world's projects a schedule update every 2 weeks and a full project update every month is adequate".
In our practice 99% of construction projects are updated at least once in a week, and daily in STO projects.
Project team meetings with performance analysis are usually held weekly and these meetings require updated information on project status and trends for informed decision making. Projects in trouble are updated daily.
In STO time is very expensive and uncertainties can be high. So project is updated each shift.
Member for
24 years 9 months
Member for24 years9 months
Submitted by Patrick Weaver on Sat, 2025-04-19 05:29
If you want people to take note of the shedule and actually try to work to the schedule changing it every day is counterproductive if your project is running for more then a couple of weeks. What's needed is action to get back onto schedule from the project team: https://mosaicprojects.com.au/PMKI-SCH-014.php#Process6
For 99% of the world's projects a schedule update every 2 weeks and a full project update every month is adequate to understand where the project is and overall trends - the rest of the time the focus should be on working the schedule.
Member for
24 years 9 months
Member for24 years9 months
Submitted by Vladimir Liberzon on Wed, 2025-04-16 22:16
But we prefer to collect not percent complete but volumes of work in physical units (m3, m, t, etc.) that were done at any reporting period. Volumes are measurable, percents are subjective.
Actual data can be imported from Excel but it is easier to fill table form created by Spider Project.
At the moment for each in progress activity, the known historic datapoints are date started, current data date and percent complete. The date started and current percent complete can be imported from Excel.
In order to accurately draw an "s" curve, you need to preserve the percent complete for each data date. Thic can be done by creating what P6 calls a Financial calendar, and then running the process called Store Period Performance .
BUT the smallest interval in a Financial Calendar is one week. Daily progress figures are not supported.
At the moment for each in progress activity, the known historic datapoints are date started, current data date and percent complete. The date started and current percent complete can be imported from Excel.
In order to accurately draw an "s" curve, you need to preserve the percent complete for each data date. Thic can be done by creating what P6 calls a Financial calendar, and then running the process called Store Period Performance .
BUT the smallest interval in a Financial Calendar is one week. Daily progress figures are not supported.
Member for
24 years 9 monthsPatrick, I don't agree with
Patrick, I don't agree with your statement that "For 99% of the world's projects a schedule update every 2 weeks and a full project update every month is adequate".
In our practice 99% of construction projects are updated at least once in a week, and daily in STO projects.
Project team meetings with performance analysis are usually held weekly and these meetings require updated information on project status and trends for informed decision making. Projects in trouble are updated daily.
In STO time is very expensive and uncertainties can be high. So project is updated each shift.
Member for
24 years 9 monthsPatrick, I don't agree with
Patrick, I don't agree with your statement that "For 99% of the world's projects a schedule update every 2 weeks and a full project update every month is adequate".
In our practice 99% of construction projects are updated at least once in a week, and daily in STO projects.
Project team meetings with performance analysis are usually held weekly and these meetings require updated information on project status and trends for informed decision making. Projects in trouble are updated daily.
In STO time is very expensive and uncertainties can be high. So project is updated each shift.
Member for
24 years 9 monthsIf you want people to take
If you want people to take note of the shedule and actually try to work to the schedule changing it every day is counterproductive if your project is running for more then a couple of weeks. What's needed is action to get back onto schedule from the project team: https://mosaicprojects.com.au/PMKI-SCH-014.php#Process6
For 99% of the world's projects a schedule update every 2 weeks and a full project update every month is adequate to understand where the project is and overall trends - the rest of the time the focus should be on working the schedule.
Member for
24 years 9 monthsIt is possible in Spider
It is possible in Spider Project.
But we prefer to collect not percent complete but volumes of work in physical units (m3, m, t, etc.) that were done at any reporting period. Volumes are measurable, percents are subjective.
Actual data can be imported from Excel but it is easier to fill table form created by Spider Project.
Member for
9 years 8 monthsAt the moment for each in
At the moment for each in progress activity, the known historic datapoints are date started, current data date and percent complete. The date started and current percent complete can be imported from Excel.
In order to accurately draw an "s" curve, you need to preserve the percent complete for each data date. Thic can be done by creating what P6 calls a Financial calendar, and then running the process called Store Period Performance .
BUT the smallest interval in a Financial Calendar is one week. Daily progress figures are not supported.
Member for
9 years 8 monthsAt the moment for each in
At the moment for each in progress activity, the known historic datapoints are date started, current data date and percent complete. The date started and current percent complete can be imported from Excel.
In order to accurately draw an "s" curve, you need to preserve the percent complete for each data date. Thic can be done by creating what P6 calls a Financial calendar, and then running the process called Store Period Performance .
BUT the smallest interval in a Financial Calendar is one week. Daily progress figures are not supported.