Issue Summary

The Investment Vs Spend report's PI Estimated Spend and total Investment and Spend - Estimated Spend are calculated slightly differently, but the slight difference isn't clearly traceable from the documentation.

The ask here is to provide more detail on how to trace the value calculations, as any team looking to start on Financials needs perfect adherence to sprint planning, member allocations, and velocity calculations in order to have both values match.

New implementations are very unlikely to have that perfect adherence and can be put off by the mismatched values, reducing adoption likelihood.

Steps to Reproduce

1. Create teams with different member allocations and velocities, including a team with 0 velocity
2. Assign the work of these teams to the same Themes
3. Assign Forecast Estimates to the Features and Epics of these most of these teams
4. The PI Estimated Spend is likely to be lower than the total sum for Investment and Spend - Estimated Spend due to Program Spend per Point being incorrect.

Expected Results

Investment Vs Spend calculation is easier to trace through work items or the barrier to entry is lower for teams just getting started with full adoption of Agile approaches.

Actual Results

The Investment Vs Spend report will calculate values based on any information entered for Forecasts and Spend values on any work items but does not inform the user that the values may be off because of outliers

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available