Forum Discussion
What algorithm does MS Project use when calculating BCWP
Specifically I'm interested where the Earned Value Method is set to Percent Complete.
I have been having a play around with a couple of simple short duration tasks.
- Each is 10 days where the work is front loaded before being baselined.
- I set the status date half way through.
- On the first task I recorded progress pretty much to plan.
- On the second task I delayed the start by 4 days then in the one day left of the week I only recorded actual work equivalent to half that was planned on the first day. I also extended the duration of this task to 20 days.
When looking at the Time-Phased EV fields in a Task Usage view on the first task I see what I expect to see.
On the second task I see Cumulative Percent Complete as 5% (correct for one day in 20). If it had followed baseline duration then it would be 10% rather than 5%.
However the BCWP for the task is a bit more than the half the BCWS for the first day of the task. Given that the actual work was half of the baseline work, I would expect BCWP to be half of BCWS.
For Earned Value Method = Percent Complete, MS Project obviously takes into account:
- Baseline Duration
- Time-Phased Baseline costs
- Current Duration
- Cumulative Percent Complete
There may be more that I have not considered but is there any documentation I can reference that describes the algorithm that Project uses in calculating BCWP so I can get a better understanding of what to expect.
Thanks
2 Replies
Hello Gilgamesh1964 ,
Here is the article on how BCWP is calculated: https://support.microsoft.com/en-us/office/bcwp-earned-value-or-ev-fields-e0c570ea-9c7b-4864-8a6b-920ed0f7b847
Paul
- Gilgamesh1964Brass Contributor
Thank you for responding but I am getting some results that don't align with that description.
(I hope you are able to read the attached images)
These two tasks were identical when baselined, it is the actuals and remaining work forecast that differs.
I believe the top one is behaving as per that description you referred to, but I would expect the bottom one to have a BCWP of $5.50 rather than $5.61.
This was done with:
Microsoft Project Online Desktop Client MSO (16.0.14326.20936) 64-bit
Version 2108 (Build 14326.20962 Click -to-run)
(This is from the Semi-Annual Enterprise Chanel)
It was getting this result that lead to my initial post.
I repeated the same test with
Version 2204 (Build 15128.20248)
Microsoft Project 2016 MSO (Version 2204 Build 16.0.15128.20240) 64-bit.
(My home version of MSP 2016 Professional)
With this second test I get the expected result of $5.50 on the second task.
Is this a bug with the Microsoft Project Online Desktop version?