What level do you track earned value for your projects? Too high is a problem, and trying to decompose work packages prematurely is problematic too. So how do you get the best of both worlds? Here's how.
I suggest you view this in 720 HD, full screen so you can see everything in the tutorial clearly. Note: Around 5:30 you'll notice in Step 3 I mis-labeled the last column. It should be PV (Planned Value) and not EV (Earned Value).
What if on Component A you do your rolling wave breakout of steps for Jan where you have your initial platforms and features and then in Feb (or out months) you add or remove steps. How would you go about re-distrubuting your EVM % weights? Especially if you claimed credit for one of more steps.
Josh NankivelEngineering Project Manager| AppleSioux Falls, Sd, United States
If you claimed credit, you can't touch it. But anything going forward can be refined with this iterative re-plan.
If new scope surfaces and a change request against the baseline gets approved, then you can re-baseline to add additional effort in, but normally you'd just want to re-plan. EVM should be used IMO to help determine if a large project will finish on time and on budget, but only at a macro level. Being so strict that you don't allow frequent (and painless as possible) re-plans at the detail level means you are using EVM for something it wasn't designed to do.
