Documentation for GreenHopper 6.2.x. Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn more.

Skip to end of metadata
Go to start of metadata

(info) Note that this page only applies if you are using the Classic Boards (which are no longer being actively developed; read more).

Overview

Scrum is a methodology that improves team communication and the incorporation of customer feedback during the development of a product's 'major version'. Typically in Scrum, the period of time required to develop a major version is broken down into smaller time chunks known as 'sprints', each of which represents a tangible 'development milestone'.

When using Scrum on the Classic boards, sprints have the following characteristics:

  • A major version and its sprints are set up as versions in GreenHopper.
  • Each sprint is typically a shorter period of time within its major version's time frame.
  • Each sprint is a 'child' of a major version.
  • A sprint has no child versions of its own.
  • Time-tracking statistics and charts are calculated per sprint, using the sprint's Start Date and End Date.

About nested child versions:

GreenHopper Classic allows you to nest child versions to provide flexibility in Scrum project management. For example, you might want to group all issues that need addressing in a major product version at the highest level of a version hierarchy. Since you might have separate teams, each working on different components that constitute this major product version, you may wish to represent each of those components as an immediate child ('component') version of the major product version. From here, you may wish to break up a given component into sprints, depending on the amount of work required to develop it. Therefore, each of these sprints would be an immediate child ('sprint') version of its respective 'component version'.

About time-tracking on the Classic boards

Note that the time-tracking statistics and charts in GreenHopper are different from JIRA. JIRA time-tracking is calculated per issue, regardless of Fix Version. The JIRA Time-Tracking report is calculated using the Fix Version, regardless of the GreenHopper Start Date and End Date. For more information about time tracking in JIRA and the relationship between logging work and time estimates, please refer to Logging Work on an Issue.

In the GreenHopper (Classic) implementation of Scrum, there are two types of hour burndown charts:

  • Sprint Hour Burndown Charts — show a timeline of the total work logged on the issues which belong to that sprint, and changes to those issues' Remaining Estimate fields.
  • Aggregate Hour Burndown Charts — show a timeline of the total work logged on all issues that belong to a major version. This includes all issues belonging to the major version's sprints. In these charts, the time spent working on issues is aggregated together from all issues in the major version's sprints, across the entire period of that major version.
  • No labels