I have a Portfolio Team. Members of that team mark their vacation time there. And my expectation is that when Portfolio does calculation of the forecasted velocity, it takes into account not simply just an average of "Story Points Closed" for several previous sprints, but it also includes past availability into the calculations.
E.g. each "Story Points Closed" is normalized to 100% availability using the actual availability of the team. If 13 Points is achieved with 50% of the team then in fact team is capable of consuming 26 points with 100% availability.
But instead I see that velocity is forecasted as a simple average... past team availability is ignored. The result is quite silly - if I'm adding more staff to the team, it is not reflected in the forecasted velocity correctly. I have to re-calculate manually which completely defies the whole point of the forecasting functionality.
Am I using the tool incorrectly? Is there any special config or a magic button to make it work as I'm expecting :)
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.