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

As a project manager I can compare the scope against a baseline

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 6.0
    • None
    • 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.

      Greenhopper calculates scope of a version based on the issues that are related to a version.
      This is very handy to visualize scope increase (or decrease) using the chart board.

      What is missing is the concept of a baseline, so that you can compare the
      scope against what was initially committed to.

      When we are running a sprint we do 'in-flight replanning' meaning that we are moving
      some stories back to the product backlog because other stories are taking more
      time, or because stories are 'below the line'

      At the end of the sprint, I'm getting questions like 'at the start of the sprint
      we had initially 520hours committed, but the current graphs shows only 460 hours'

      At that moment it would be very useful to be able to show:
      This is the list of issues we took initally in the iteration, and these have been dropped
      'in-flight', to be able to deliver the other priorities, or the way around,
      'during this sprint following stories have been added to the iteration'

          Form Name

            [JSWSERVER-1815] As a project manager I can compare the scope against a baseline

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3067077 ] New: JAC Suggestion Workflow 3 [ 3662858 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Component/s Original: ↓ Obsolete -- ChartBoard (Classic) [ 12966 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2622961 ] New: JAC Suggestion Workflow [ 3067077 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2322611 ] New: Confluence Workflow - Public Facing v4 [ 2622961 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2040426 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2322611 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032903 ] New: JIRA PM Feature Request Workflow v2 [ 2040426 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 738718 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032903 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Backlog Order (Obsolete) Original: 580000000
            Workflow Original: GreenHopper Kanban Workflow v2 [ 300496 ] New: JIRA PM Feature Request Workflow v2 [ 738718 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Shaun Clowes (Inactive) made changes -
            Fix Version/s New: 6.0 [ 27108 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

              Unassigned Unassigned
              da0b846da3a7 francis
              Votes:
              19 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: