Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9634

Line chart for projected backlog completion with optimistic and pessimistic

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      I as a Product Owner or Scrum Master want to see a report generated by Greenhopper/JIRA Agile which shows the projected completion for the current backlog items so that I can better understand what the overall project status is today.

      Further thoughts:

      • able to select which epics to include as "total backlog"
      • calculation based on story points
      • configurable average velocity (how many or which past sprints to consider for average)
      • utilize average velocity to calculate projected completion
      • show how many sprints until completed
      • show optimistic and pessimistic line
      • configurable optimistic and pessimistic calculation (percentage)

      I'm doing this today in Excel based on data I'm extracting out of JIRA.
      This is the most important chart for our project and helps everybody involved to better understand where we at and take actions early to influence the project for the better.

      Attaching an image of the chart I'm creating in Excel at the moment.

        1. Project-Status.png
          Project-Status.png
          121 kB

            [JSWSERVER-9634] Line chart for projected backlog completion with optimistic and pessimistic

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3066899 ] New: JAC Suggestion Workflow 3 [ 3661348 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2625179 ] New: JAC Suggestion Workflow [ 3066899 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327213 ] New: Confluence Workflow - Public Facing v4 [ 2625179 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2044037 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327213 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032200 ] New: JIRA PM Feature Request Workflow v2 [ 2044037 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736220 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032200 ]
            Martin (Inactive) made changes -
            Business Value Original: Exceptional [ 10503 ]
            Workflow Original: GreenHopper Kanban Workflow v2 [ 549065 ] New: JIRA PM Feature Request Workflow v2 [ 736220 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Martin (Inactive) made changes -
            Epic Link New: JAGDEV-905 [ 319776 ]
            Tom Kotecki (Inactive) made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Tom Kotecki (Inactive) added a comment -

            Many thanks for reporting this issue. As mentioned earlier here, this functionality is partially supported by today's Epic and Version reports. We are looking at improving them in the near future, specifically one of the improvements we're looking for is using sprint velocity to project how many sprints are left to complete a Version or an Epic.

            Please keep an eye on those improvements in the upcoming releases of JIRA Agile, and let us know if they meet your requirements.

            Kind regards
            Tom Kotecki
            Product Manager, JIRA Agile

            Tom Kotecki (Inactive) added a comment - Many thanks for reporting this issue. As mentioned earlier here, this functionality is partially supported by today's Epic and Version reports. We are looking at improving them in the near future, specifically one of the improvements we're looking for is using sprint velocity to project how many sprints are left to complete a Version or an Epic. Please keep an eye on those improvements in the upcoming releases of JIRA Agile, and let us know if they meet your requirements. Kind regards Tom Kotecki Product Manager, JIRA Agile

              Unassigned Unassigned
              f4119c0c41c7 Ronny Katzenberger
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: