L
Langhorne
We are attempting to track various EVA metrics over time, and there are two
ways to do it: One, capture the EVA metrics week by week right after we
update and publish the schedule (we're in a Project Server environment); Two,
reset the Project Status date week by week from the most recent published
schedule and capture the EVA metrics per the status date. Comparing the two
approaches, BCWS is identical each week, ACWP is close, and BCWP is very
different. Because BCWP is so different, SPI and CPI end up being different
also. In fact, with method One we see them going down, and method Two shows
them going up.
Any idea why this would be the case? Is one or the other a best practice
for tracking EVA over time? (We're using Project and Project Server 2003, by
the way).
Thanks in advance...
- Langhorne
ways to do it: One, capture the EVA metrics week by week right after we
update and publish the schedule (we're in a Project Server environment); Two,
reset the Project Status date week by week from the most recent published
schedule and capture the EVA metrics per the status date. Comparing the two
approaches, BCWS is identical each week, ACWP is close, and BCWP is very
different. Because BCWP is so different, SPI and CPI end up being different
also. In fact, with method One we see them going down, and method Two shows
them going up.
Any idea why this would be the case? Is one or the other a best practice
for tracking EVA over time? (We're using Project and Project Server 2003, by
the way).
Thanks in advance...
- Langhorne