Loading Profile...
Twitter,
Facebook, or email.
EMPLOYEE
Why is the "forecast completion" checkbox disabled on my Release Forecast Report?
Official
Response
-
If "forecast completion" is disabled, ScrumWorks cannot get the Velocity Trendline to converge with the Work Added Removed Trendline.
In your product there's a historical trend of new work being added faster than you've been completing it. If you believe this is incorrect, check to see if you have forgotten to mark backlog items as done, or use the Product Backlog Item Editor's "History" tab to back-date backlog items that were entered into ScrumWorks too long after they were originally identified. If some of the items in your Product Backlog are low-priority "wish list" things, create a separate Release called "Wish List" and exclude that release from the burndown chart.
-
If "forecast completion" is disabled, ScrumWorks cannot get the Velocity Trendline to converge with the Work Added Removed Trendline.
In your product there's a historical trend of new work being added faster than you've been completing it. If you believe this is incorrect, check to see if you have forgotten to mark backlog items as done, or use the Product Backlog Item Editor's "History" tab to back-date backlog items that were entered into ScrumWorks too long after they were originally identified. If some of the items in your Product Backlog are low-priority "wish list" things, create a separate Release called "Wish List" and exclude that release from the burndown chart.Comment -
-
What if we had already started a project and the PBIs were added retrospectively and therefore appear as churn, incorrectly. How can we make the tool see them as being in the PB before the sprints started? -
-
I believe you would want to try addressing the estimate history for the PBI. The steps for this can be found here:
http://www.danube.com/docs/scrumworks... -
