Hi Matt,I think there might be a flaw in your logic. Even for a child, the only way to know 'a predicted' end date is to know the rate at which work is being done and how much work there is left to do. Otherwise, the child's enddate is still just someones guess.To help answer some of these sorts of questions, I developed two apps. The first give you a burnup/burndown for portfolio items. The burndown gives a desired (green line) and a calculated prediction line (grey dashed) as long as the work rate being completed is faster than the rate of work being added (else you can predict diddly-squat).The second app will look at the current delivery rate of your past portfolio items and give you metrics on how well you are predicting and how long a new project might take you (from your initial size guesses).
Have a look here:https://github.com/nikantonelli/WorkItemsForInitiativehttps://github.com/nikantonelli/ForecastAccuracyThere is a third app that you might also find useful as it will highlight for you where you have child dates outside the range of the parent dates.https://github.com/nikantonelli/PortfolioItemTimeLine/tree/With-Stories