S
ST
Hi,
We are using MSP 2003 Pro I am looking for a way (a workaround or an
approach) to measure some kind of schedule performance, do you have any
suggestions...
There are 2 reasons why we do not rely on MS Project's SPI field:
1) We prefer not to allow PMs to manage baselines, so an administrator
manages baselines.
2a) After a baseline is set, if a PM breaks out tasks and adds supporting
details there is no SPI calculation for these new tasks. Rebaselining new
tasks would mean more administration for the persons managing baselines.
2b) A PM can delete a task that has a baseline with no warning, so the
SPI would be corrupted.
2c) a PM can use tasks that have a baseline to create new tasks, but that
would mean they have created new tasks with baselines that we not formally
done by the baseline administrator.
Any suggestions?
Thanks in advance,
/Spiro Theopoulos
We are using MSP 2003 Pro I am looking for a way (a workaround or an
approach) to measure some kind of schedule performance, do you have any
suggestions...
There are 2 reasons why we do not rely on MS Project's SPI field:
1) We prefer not to allow PMs to manage baselines, so an administrator
manages baselines.
2a) After a baseline is set, if a PM breaks out tasks and adds supporting
details there is no SPI calculation for these new tasks. Rebaselining new
tasks would mean more administration for the persons managing baselines.
2b) A PM can delete a task that has a baseline with no warning, so the
SPI would be corrupted.
2c) a PM can use tasks that have a baseline to create new tasks, but that
would mean they have created new tasks with baselines that we not formally
done by the baseline administrator.
Any suggestions?
Thanks in advance,
/Spiro Theopoulos