Effective project management in an agile environment relies on clear work definitions and robust tracking tools like Jira. This post reviews the fundamental components of Jira work items and the key charts used in Scrum to monitor progress and plan team capacity.
Understanding Jira Work Item Types
A Jira "issue" or "work item" defines a piece of work that must be completed. The purpose of using a tool like Jira is to break down activities into small, manageable chunks that can be assigned and tracked. The three common types are:
- Task: A generic activity type; almost any piece of work that needs to be done can be categorized as a task.
- Bug: Associated with defects, typically in software development, when something is not working as expected.
- Story: A work item type associated with agile methodologies like Scrum or Kanban. Stories are used because they tie into the concept of story points, which are numerical values assigned to estimate the work effort or complexity.
Sprint Mechanics and Progress Tracking
Scrum is an agile methodology that uses the concept of a Sprint, defined as a fixed-duration iteration, typically lasting one, two, or three weeks. The main objective of a Sprint is to create focused iterations by selecting high-priority items from the backlog and delivering them within that fixed duration.
The total number of story points for all selected stories constitutes the team’s commitment for that sprint. For instance, a commitment might be to deliver work effort worth 35 story points.
Progress against this commitment is tracked using a Burndown Chart, a popular graph in Jira Scrum boards.
- The chart plots the remaining story points against time.
- The ideal plan is represented by a grey line showing a linear decrease in remaining points, aiming for zero remaining points by the end of the sprint.
- The red line represents the reality. Ideally, the red line should follow the grey line, but any deviation allows for early course correction. The amount decreases as the team "burns the story points" by completing stories.
Capacity Planning with the Velocity Chart
For new teams, their capacity is initially unknown, but it is determined over time using the Velocity Chart. This chart calculates the team's capacity by averaging the story points actually delivered in past sprints (not the amount committed).
For example, if a team delivered 25 points in Sprint 1 and 25 points in Sprint 2, their average velocity is 25.
Project managers must use this velocity data to plan future sprints realistically, avoiding the mistake of committing to more work than the team is capable of finishing. Analyzing the velocity chart ensures that the team's capacity is respected, making it an extremely helpful tool for new managers and those working in Jira management and consultancy.
