Multiple Updates By Status Date - Save Between Necessary? RRS feed

  • Question

  • Hello, All.

    I have to perform updates for several schedules and each schedule will need data for several Status Dates.

    Is it necessary to save each Status Date update before entering the data of the next Status Date?

    Is there a way to perform several Status Date updates efficiently in a single schedule?

    Thank you all in advance.
    Monday, November 30, 2015 12:38 AM

All replies

  • del_ops,

    I'm a little confused. Are you trying to play "catch up" because the plan didn't get updated periodically when it should have (i.e. at each status period)?

    If you are not doing some type of "catch up", then please give us more information about what you mean by "several status date updates".

    Whether you save or not for each status date depends on what data you need to preserve (e.g. earned value metrics for each status period). If you don't need to present or preserve any metrics, then why not just jump to the latest status update period and skip the updates that didn't get done when they should have. However, if you do not to preserve metrics for each update that yes, you should save each update, probably using Save As with a date stamp in the file name.

    However another important factor may override any of the above. It is always good practice to save often. The last thing you want a a ton of updates that your spend a ton of time doing and then have a power glitch or some other unfortunate thing happen that causes all the data to be lost or corrupted when you finally try to save.


    Monday, November 30, 2015 2:42 AM
  • For a particular project, it is a mistake to only have one file and constantly over-write it with improvements, re-estimates and new information and status updates during the course of the project execution. You lose the history of the project. Save a version every day. Then you can never lose more than 24 hours worth and you have the entire history. It is only a matter of establishing a routine and some discipline and a sensible file naming convention, and takes no effort to save 300 incremental versions of the same plan during a 300 day project, and the cheapest thing in the world is hard disk space.

    When updating and re-scheduling, do it regularly and frequently, such as every Thursday Afternoon at 17:00. Catch-up is much harder, if not impossible.

    Can you do what John says and ignore all of the previous status dates except this one right now, and establish the current progress status of what has been done up to now? Give us an idea of the timescales.

    Monday, November 30, 2015 6:53 AM