Shall be an update that includes whatever happened up to the closing date.
To say that at closing dates suddenly all activities stopped is hard to believe, most probably these activities finished at some time before project end.
Any started activity must have a finish date before project closure.
A project that have unfinished activities is an unfinished project and not a closed job.
Activities or portions deleted on any update have no place in such schedule; freeze them on a baseline.
It makes no sense keeping hundreds of activities if a building on a job is taken out of the contract.
It makes no sense keeping hundreds of activities if the building design changes radically because of unforeseen soil conditions or for whatever reason.
Keeping no longer existing activities makes no sense.
Use Baseline functionality to record schedule just before the work stoppage or store under a separate file name.
After a project is closed whatever happen in the future belongs to another project otherwise it is not true it was a closed project.
The last schedules update shall be an update that reflects your final reconciliation of the project budget. If activity duration is reduced it does not mean all budgets are automatically reduced. This can become an issue when analyzing the portfolio schedule.
In summary:
You shall not leave it as is.
Started activities must show a finish date prior to closing date.
Budgets shall be reconciled.
Activity that has not started and will never do has no place in any schedule update.
Spider Project allows you to display deleted activities on a conspicuous way when comparing schedule versions and without the risk of interfering with current schedule, easy and transparent. If your software lacks enough functionality it is no excuse to promote such misleading and error prone practice.
Member for
21 years 8 months
Member for21 years8 months
Submitted by Rafael Davila on Fri, 2017-07-28 12:15
In unfinished projects the practice to keep deleted activities is even worse.
GAO Schedule Assessment Guide Best Practices for Project Schedules suggests keeping deleted activities and logic while setting duration to 0. See page 140 of 240.
GAO is wrong, leaving deleted activities as well as leaving the original logic in place is not best practice:
It is a poor workaround used when your software is incapable to show activities in included in one schedule version but not in another.
I am not surprised with GAO recommendations as they are biased in favor of software incapable of dealing with comparison of schedules with deleted activities.
Leaving deleted activities can distort cost loading if you if you miss to delete any fixed cost assignment.
Leaving deleted activities can be confusing and misleading
Incoming/outgoing remaining lags might need to be adjusted, mere change in activity duration do not tackle this issue.
Leaving deleted activities can lead to wrong logic; it is a lazy scheduler approach.
Member for
16 years 4 months
Member for16 years4 months
Submitted by Zoltan Palffy on Thu, 2017-07-27 14:18
ok but first make a copy of the schedule and leave it as it just in case it reopens. It cant hurt. Name the project junk for superceeded something like that
I presume the best option would be to make finish/start date of the activities that have NOT started equal to the date when the project is closing and the finish date of activities that have started equal to the date when the project is closing, too.
The reporting team are not happy to see the finish date of the closed project in the future, so options 2 and 3 are applicable to my case. Of course, if the project is likely to be re-opened, other options are acceptable but if the project has been closed permamently, options 2 and 3 are the best.
Member for
16 years 4 months
Member for16 years4 months
Submitted by Zoltan Palffy on Wed, 2017-07-26 14:35
Leave it as is. This way if the project ever re-starts you know what still need to be done as per the original scope.
option #2
for every activity that has started but has not finished make the actual finish date equal to the date that you were instructed to Stop and put a note in the notebook tab saying what you did and why
option #3
or every activity that has NOT started and has not finished make the actual start and actual finish date equal to the date that you were instructed to Stop and put a note in the notebook tab saying what you did and why. You can do this with a global change.
Option #4
Leave it as is and for activities that are started but not done and or not started and not done and put a note in the notebook tab
Option #5
Leave as is and in the Project Name say that the project was closed on such and such a date
Member for
21 years 8 monthsAmong other things the last
Among other things the last schedules update:
Spider Project allows you to display deleted activities on a conspicuous way when comparing schedule versions and without the risk of interfering with current schedule, easy and transparent. If your software lacks enough functionality it is no excuse to promote such misleading and error prone practice.
Member for
21 years 8 monthsIn unfinished projects the
In unfinished projects the practice to keep deleted activities is even worse.
GAO Schedule Assessment Guide Best Practices for Project Schedules suggests keeping deleted activities and logic while setting duration to 0. See page 140 of 240.
http://www.gao.gov/assets/680/674404.pdf
GAO is wrong, leaving deleted activities as well as leaving the original logic in place is not best practice:
Member for
16 years 4 monthsok but first make a copy of
ok but first make a copy of the schedule and leave it as it just in case it reopens. It cant hurt. Name the project junk for superceeded something like that
Member for
8 years 3 months.
.
Member for
8 years 3 monthsThank you for your reply.I
Thank you for your reply.
I presume the best option would be to make finish/start date of the activities that have NOT started equal to the date when the project is closing and the finish date of activities that have started equal to the date when the project is closing, too.
The reporting team are not happy to see the finish date of the closed project in the future, so options 2 and 3 are applicable to my case. Of course, if the project is likely to be re-opened, other options are acceptable but if the project has been closed permamently, options 2 and 3 are the best.
Member for
16 years 4 monthsyou have several
you have several options
option #1
Leave it as is. This way if the project ever re-starts you know what still need to be done as per the original scope.
option #2
for every activity that has started but has not finished make the actual finish date equal to the date that you were instructed to Stop and put a note in the notebook tab saying what you did and why
option #3
or every activity that has NOT started and has not finished make the actual start and actual finish date equal to the date that you were instructed to Stop and put a note in the notebook tab saying what you did and why. You can do this with a global change.
Option #4
Leave it as is and for activities that are started but not done and or not started and not done and put a note in the notebook tab
Option #5
Leave as is and in the Project Name say that the project was closed on such and such a date