Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-89030

Improvement for Portfolio Themes Report.

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Timed out
    • Plans - Timeline
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      As an executive who views Portfolio reports, I want to see how much of my teams efforts are being spent on different focus areas (themes) for my upcoming release. The teams have the same Sprint cadence and the release date is fixed, such that all teams have to release to our customers at the same time. The Sprint lasts for 2 weeks, and the release cycle consists of 3 Sprints (6 weeks). Each team member works for 40 hours a week.

      The teams have different Velocities; Pineapples Team (5 people) deliver 20 points a Sprint and Grapes Team (also 5 people) deliver 200 points a Sprint. The teams are working on different focus areas; both are equally important to our customers, and based upon the team's estimates will take the entire release to deliver. As such the target for each theme is set to 50% each.

      Currently, the estimate shows that ~91% of focus will be spent on Grapes theme, ~9% of focus will be spent on Pineapples as the report blindly adds Story points and treats them all as equal when they are not (and never should be considered in that way!)

      What we need is to take into account both the estimates on the Epics/Stories/Tasks and the team velocity, in order to be able to compare apples to apples and look at the focus (themes) across the whole projects.

              Unassigned Unassigned
              aschneider@atlassian.com Adalberto Schneider
              Votes:
              4 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: