IP Sprints affecting Team Capacity and Velocity

XMLWordPrintable

    • Type: Bug
    • Resolution: Not a bug
    • Priority: High
    • None
    • Affects Version/s: 10.111.3
    • Component/s: Time - Sprints

      Issue Summary

      Team Capacity and Team Velocity should not be calculated with points from Innovation and Planning Sprint

      Steps to Reproduce

      1. Create Feature composed by 5 Sprints. Last Sprint to be considered as Innovation and Planning.
      2. Assign stories to Team A of 30 points in each Sprint from Sprints 1 to 4 that will be delivered by Team A.
      3. Assign a story of 5 points to Team A in Sprint 5 to complete the Feature.
      4. Team A will have Capacity and Velocity of 25 points for next Program Increment [(30 + 30 + 30 + 30 + 5) / 5 = 25] because the calculation considers the Innovation and Planning Sprint.

      Jira Align ideally needs to be fixed to operate as originally intended to support the SAFe IP sprint concept. If a sprint is created in a PI object as an IP sprint then that sprint must be excluded from average velocity calculations, BUT all work completed in the IP sprint must be included in the completed work for the PI.

      Expected Results

      Considering SAFe concept, Team capacity/velocity on the above scenario should be:
      (30 + 30 + 30 + 30) / 4 = 30
      (Sum of points delivered per sprint NOT including Innovation and Planning / Number of Sprints NOT including Innovation and Planning)

      Actual Results

      Current calculation based on the scenario above:
      (30 + 30 + 30 + 30 + 5) / 5 = 25
      (Sum of points delivered per sprint including Innovation and Planning / Number of Sprints including Innovation and Planning)

      Workaround

      No workaround available

            Assignee:
            Don Fuller
            Reporter:
            Andre Deme
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: