Need Best Practices for Release planning in 2.0, now that Originally Planned is gone

[Georgianne Rogers]

We were using Classic plans for 6 months and are in process of moving to Portfolio 2.0 Live Plans. An issue we are having is that we were doing high level estimating on the Epics, and saving that to the Originally Planned field. Then, when the child issues and stories were estimated we could compare the original estimate to the current one. Without having the Original Estimate, we are at a loss for how to do this, especially since the behavior on Epic estimates also changed. Will you bring back the Originally Planned field?

In Classic plans, the Epic estimate would become a summation once child estimates were added. Now it's adding both Epic and Child estimates together which is overstating the total estimate.   I'm confused why you would add them together - the Epic estimate should be a summation of the child estimates only not in addition to the child estimates.

Please suggest best practices for how to do high level planning - do you suggest we wipe out the Epic estimate once we start adding child story estimates? How did you envision this would be done in 2.0?

[ErikB]

Hi Georgianne, we're having the exact same issue here and I actually just did a similar post and found yours afterwards. One related question for you: when you start adding child stories (and their estimates), are you able to add them all at once to cover your entire Epic, which then gives you a total detailed estimate? Or do you just add a few child stories in the Sprints as you go, until the full Epic is covered? It's been the latter here, so it's difficult to get the detailed estimates for the entire Epic from the beginning. Thanks,