Versioning control of schedules

[Maxwell Anderson]

Hello,

Is there a way to make the control of versions of the schedules of a
project? Ideally, every change of schedule was a saved version.

I thought to hold the control of versions by the name of the project,
but is not a good idea because I must build reports using Reporting
Services.

Do you know any appropriate procedure?

Thanks

 

[Dale Howard [MVP]]

Maxwell --

There is no default method built into Project Server 2007 to allow the
versioning of enterprise projects. Hope this helps.

 

[Maxwell Anderson]

Dale Howard, thank you for your reply.

We are implementing the CMMI in our company and one of the
requirements of the consultancy is the control of versions of a
project.

I thought about building something, using VBA in Project Professional,
building filters, I do not know for sure.

I thought also to save several projects in Project Server and build
filters to view the latest project.

Someone has had the need to build something? Some initial idea?

Maxwell Anderson

 

[Dale Howard [MVP]]

Maxwell --

Although there is no automatic way to do this, how about using a process
similar to the following:

1. After every round of updates to an enterprise project, do a final save
of the project to the Project Server database.
2. Then click File - Save As - Save as File and save the current version as
an MPP file.

In step #2 above, you would need to establish some type of naming convention
for the files, and a common file location for a previous versions of a
project. Just a thought.

 

[Maxwell Anderson]

Very good! I also thought about it, just did not know whether there
was a better way.

I will build this.

Thank you very much Dale.

 

[Mark E. Read]

Very good! I also thought about it, just did not know whether there
was a better way.

I will build this.

Thank you very much Dale.

I have to chime in and ask a couple of questions (assuming you are
using Project Server 2007)

1) What about using the administrative backup and configuring it to
save the last 10 versions? Is that enough? Too bad you can't name
them, however they are timestamped.
2) How about having a mature baseline policy and using Baseline 0-10?
This doesn't save tasks, but cost, duration, work, start and finish
are pretty good!

Just some thoughts from the left coast.

Cheers!

--Mark

 

[Maxwell Anderson]

Hello Mark

Thank you for your reply.

Today we used the Baseline 0-10, but what we need really is to save
the tasks in a version so we can make comparisons.

On the administrative backup, maybe it would not be a good idea. I do
not know for sure, but I will check.

Project Pro 2007 has a toolbar to make comparisons between projects.
Unfortunately several versions of a timeline can not be saved in a
single project file.

Any other idea will be of great benefit.

Maxwell Anderson Ielpo Amaral