E
Esteban
On EPM it is possible to save versions of mpp files but (as far as I know)
doesn't keep record of all check-in/check-out instances. Problems this may
represent:
If you make changes to a project file, it is not possible to fall back to
the latest file (thus if the project schedule is updated by 2 or more PMs it
wouldn't be possible to recover a single file on any given date the file was
checked-out).
When there are changes in product development requirements, often times
there is a need to evaluate the impact on the project schedule. PMs could
save the published version of the mpp file under other versions trying to
simulate such impact. After a number of modifications we may end up under the
7th version of the mpp file, which we consider at this stage to be the one we
would like to have as published. How do we go about it?
doesn't keep record of all check-in/check-out instances. Problems this may
represent:
If you make changes to a project file, it is not possible to fall back to
the latest file (thus if the project schedule is updated by 2 or more PMs it
wouldn't be possible to recover a single file on any given date the file was
checked-out).
When there are changes in product development requirements, often times
there is a need to evaluate the impact on the project schedule. PMs could
save the published version of the mpp file under other versions trying to
simulate such impact. After a number of modifications we may end up under the
7th version of the mpp file, which we consider at this stage to be the one we
would like to have as published. How do we go about it?