BCWS Incorrectly Calculating at the Project Summary Level

[Spencer Lamoreaux]

Hi -

I'm using MSPS 2007. When I publish the project, the project summary
task has a BCWS of $10,821 and SPI is .81. If I re-open the project
and no updates have been submitted via PWA, the SPI/BCWS values remain
the same.

However, if a team member submits updates and I accept them (in PWA),
the BCWS at the project summary task only (row 0) falls to $5,228. The
row 1+ summary tasks show that the BCWS should still be $10,821. But,
something causes the summary task calculation for BCWS to fall and
with that the SPI shoots to over 2.4 thus resulting in a loss of
confidence from the project team and management on the viability of
MSPS.

Any ideas why this is happening? Prior to the IU patch, we didn't seem
to have this issue. FYI - Status date is NA in both cases and the
'updates' are minimal not pushing out any tasks.

Thanks in advance for any insight.

Spencer Lamoreaux
Intel IT Scheduling Product Manager

 

[Jack Dahlgren MVP]

Status Date should NEVER be NA if you are using earned value.

Set it correctly and see what happens.

-Jack Dahlgren

 

[Spencer Lamoreaux]

Set the status date and it didn't make a difference. This all started
happening after we applied the infrastructure update from Microsoft.
And, it's happening several projects in our production environment.

Any other ideas? This is driving PMs crazy since our org indicators
and reports are based on SPI/CPI.

-Spencer