Sprint Burnup Burndown Chart Gadget Doesn't Keep Ideal Burndown Constant At Point in Time

[JD Lobue]

When a plan is created at a point in time, the ideal burndown should be locked down at the point in time, and any new work that is created should only change the remaining trend line. What you all are doing below is that if new scope is being added after the point in time, you are shifting the ideal trend line up to that increased scope prior to the date in which the scope was added. This is incorrect. You can see from my example that on 7/1, a plan of work was determined around 70 issues, and then team increased scope. What you are doing is moving the ideal burndown from the plan to that new increased scope. Increased scope should not change the original ideal trend because that original ideal trend is based on the scope at that time. If anything the new trend line should change only after that new increased scope, and not from the original time of 7/1 in this example. Can you change ideal burndown calculations after increased scope at a later time? You can see below that my red line should be the ideal trend based on the 7/1 scope. If you can change the trend line calculation at a later time, say 7/14, when new scope is added that would be great. However, if you cannot, then changing the ideal trend because of added scope at a later time should not cause the ideal trend to jump up to the new added scope prior to the date the new scope was added.

‌

‌

‌

[Danut M [StonikByte]]

Hi @{5b2d16639ba6d02662e34fbd}

Starting with version 1.24.0 we added a setting that allow configuring how the Ideal Lines are calculated. This also applies for the Cloud version of the app.

You can now choose how the ideal lines are calculated: by initial scope or by current scope.

In order to obtain the behavior that you described, select “Calculate the ideal lines based on the initial scope“.

‌

This setting was added to both Sprint Burnup Burndown Chart and Release Burndown Chart gadgets.

‌

Danut

‌

‌