Archive Versions of a project.

[Frank]

You create a version type under admin.
You open the published project.
You make the changes and save the project.
If you want a archive you do a save as and choose a version.
Then save it and the publish it.

What if you want to keep a daily or weekly archive of a project that
may last a year, do you have to create a version for each? I.E. Archive
1 Archive 2 - Archive 100
What naming conventions for versions are you using?
Is their a better way?

Any input would be greatly appreciated!
Thank You,
Frank

 

[Gary L. Chefetz [MVP]]

Frank:

It strains my brain a bit trying to imagine why you want to do this.<g>
Unless you've got a pressing need to keep them in the production database,
I'd setup an off-application backup scheme where these versions were stored
in file shares, SharePoint libraries, or perhaps a separate database.
Otherwise it's an enormous amount of useless data in the system.

 

[Frank]

Implementing Project Server is a hard pill for our Project Manager's to
swallow.

The executives and our formen may benefit: One of the benefits may be
having the history of the project on the server, I really do not know!

I'm getting from your reply that keeping the information on the server
may not be the best solution.

Trying to figure out how to make the transition from stand alone
Project 2003 to the server, while making it as painless as possible, is
a daunting task.

Our Project Managers handle construction projects, currently they save
revisions as they go along. What they currently do is, a save as of
the project file with the current date at the end. By the end or the
project they may have many files.

Having the history is mandatory. It's gives us a good picture of how
the project has evolved, If a client has questions or complaints we can
go to that specific point in time.

I read in "Administering an Enterprise PMO" about version and was
trying to get sort of a best practice as to how this may apply to our
company.

So in your opion continuing to do a save as and keeping a standalone
copy of the project files would be a better practice, then making the
versions available on the project server?
What and how is version control used?

Do you know of any white papers or best practices that may relate
directly to the construction field?

Friday wahoo!!!

Thank you Gary,

Frank