Timeline for Planned / earned value for items outside of the project scope?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 9, 2021 at 21:23 | comment | added | David Espina | Well, there's the right thing to do and the right thing to do. From an EVM standpoint, I wouldn't pursue more budget for a work error but, as a seller of services, if the customer wanted to give me more budget (and fee) and let me report a better variance, I don't think I would turn it down if I was being honest with myself. | |
| Feb 9, 2021 at 21:04 | comment | added | Dan Tappin | Also a good point - the scenario I had in mind here was where the client specifically wanted the original budget changed. In hindsight I should have pushed back or just tracked it separately on my end. The project came in 'on buget'! lol | |
| Feb 9, 2021 at 21:00 | comment | added | David Espina | There shouldn't be a change request for a screw-up. If a mistake was made and rework had to occur, then the original work package never really completed and you would simply continue to accrue costs and time. That would be a variance. The rule is: no change requests for the sole purpose of removing a variance. | |
| Feb 9, 2021 at 20:53 | vote | accept | Dan Tappin | ||
| Feb 9, 2021 at 20:53 | comment | added | Dan Tappin | I would add senior management to that list of stakeholders lol. In hindsight you are right and my second statement in my post aligns with that. In my case the scenario I have in mind is where the change is a 'screw-up` and they want to quickly point to the budget and say $X over the pre-change BAC. | |
| Feb 9, 2021 at 20:47 | history | answered | David Espina | CC BY-SA 4.0 |