About this report
The Sprint Status report displays the overall progress of the sprint at the task level, providing a visual status of the stories, as well as acceptance criteria and a breakdown of task completion.
The chart is especially useful to both Scrum Masters and product owners, who are seeking an unobtrusive approach to appraising the status of the team mid sprint without the need to interrupt valuable work. This report may also be beneficial as a tool during daily stand-ups or during sprint review meetings as a mechanism for discussion.
Each row of the report is comprised of two sections, with first being a row containing hyperlinked story names, allowing access to the story details, followed by an icon with a link to story comments.
The second row of each story section, contains the value point(s) and effort point(s) expended in the sprint as well as the Estimated Total Hours / Actual Hour(s) spent over the sprint duration. Next in the row are two progress bars, colored green, red, yellow or gray indicating status. (Green 100%, Yellow<75%, Red <25% or Gray- no status).
Stories that have been split during the selected sprint will have the word SPLIT displayed in lieu of Value Points or Effort Points. (See Screenshot below.) The second half of the split story in the next sprint will have the Value Points and Effort Point displayed.
Hovering over either of the two progress bars, will reveal the count and percent complete for the development and testing tasks respectively.
At the end of these progress bars are 5 icons displaying story health, acceptance criteria, Dev Complete status, Test Complete Status and Product Owner Acceptance. Hovering over the fuel bar for story health will show a percentage of health for the story. Hovering over the second icon displays the percentage of acceptance criteria complete. The third fourth and fifth icons change color to reveal their status of each key state of the story progression. Dev Complete, Test Complete and Accepted. These are colored either yellow(incomplete) or green(complete). These icons also offer tool tips showing whom accepted the story.
- Select the Reports icon from the left Navigation menu.
- Start typing the report's name in the Search box.
- Once found, select the report.
Note: You can also use the categories on the left to search for the needed reports.
- PI must exist in the system, and be tied to a program.
- Features must be created and tied to the PI.
- Stories, with point values, must be created and tied to features.
- Stories must be assigned to the selected sprint.
- Stories must be detailed to the task level in order to drive the progress bars.
How are report values calculated?
- Value Points = Level of Value captured during planning
- Effort Points = Story Points assigned to story during planning
- Hours = Sum of Development Hours / Sum of QA Hours - all time rounded to nearest whole hour
- Development Tasks Complete % = Count of Complete Story Tasks / Count of Total Story Tasks
- Testing Tasks Complete % = Count of Complete Testing Tasks / Count of Total Testing Tasks
- Sprint Health % = Color set based on number of defects per sprint. This value is configurable by the system administrator.
- Acceptance Criteria Complete % = Number of acceptance criteria created / number accepted
- Dev Complete = reflects Dev Complete flag set
- Test Complete = reflects Test Complete flag set
- Accepted = reflects Product Owner acceptance of story
- Effort and value points for a story are credited on the day the story is accepted.
How to interpret this report
This report is a quick way to appraise the status of the team mid-sprint, provided that the teams are tasking out stories. Progress bars for both development and test activity allow for quick assessment of each story, with effort points and hour(s) being useful in assessing the scale of the of the work to be accomplished.
If used during the daily stand-up, development and test completion as well as PO Acceptance can be captured here, by clicking the appropriate colored ellipses on the right side of the report. These will toggle from yellow to green.
Bars will remain gray until 25% of development and/or Test Tasks have been completed, at which point they will move to yellow. Only when 100% of development Tasks or Test Tasks are Complete will the bars turn green.
This chart when used in conjunction with the Effort Points burn down report may be useful to compare against, or to assess story progress against sprint completion.
Join the Atlassian Community!
The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.
Need to contact Jira Align Support? Please open a support request.