Program Increment Progress (PIP) report (burnup/ burndown) does not calculate velocity override

XMLWordPrintable

    • 1

      Issue Summary

      In the program room, the customer updated override velocity in Program Increment Load widget and set it to "Actual" and go to Program Increment Progress report and check burn Details.
      The “predicted” lines do not reflect the override values but instead uses the 5-week average. Thus, the reports are misleading since the override numbers are not taken.

      Steps to Reproduce

      1. Go to Program room
      2. Enable Program Increment Load by enabling the toggle in View Configuration > Program Increment Load widget
      3. Select the cog icon on the Program Increment Load widget and set it to "Actual"
      4. Enter override velocity
      5. Go “Key Metrics”, choose “Program Increment Burndown/Burnup” and click Full Report (Go to Program Increment Progress report)
      6. Click Burn Details button

      Expected Result

      Burndown/up indicates the OVERRIDE value in optimistic/predicted/pessimistic lines.

      Actual Result

      Burndown/up indicates the AVERAGE 5-week value in optimistic/predicted/pessimistic lines.

      Additional information

      We confirmed with PM Team the current design of the report does not use the velocity override in the calculation. Engineering confirmed that this is what is in the code and aligns what is documented in the help article and recommends raising a Suggestions ticket.

            Assignee:
            Munna (Inactive)
            Reporter:
            Rachel Kim
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: