Using Jira Reports to track releases | Release Burndown Chart & Version Report

This is the fifth (and final) video in our series on Relative Estimation. In this video I cover:

- Using Jira's "Release Burndown Chart"
- Using Jira's "Version Report"
- Tips for releases running late

👉 SPRINT REPORT FOR STAKEHOLDERS
===================================
Sprint Report for Stakeholders is a tool to help you align expectations and build trust with your stakeholders. It will take the hard work out of reporting the results of your team’s Sprint by producing a well-crafted Sprint Report including the most relevant information for stakeholders, leaving them with a sense of confidence in you and your Scrum team.

Sprint Report for Stakeholders does this by reading your Sprint information in Jira and producing a report in Confluence allowing you to easily customize what’s presented, capture feedback during your Sprint Review, and share the report following the Sprint Review session.

🔗 CLICK LINK BELOW TO TRY FOR FREE:

🔔 SUBSCRIBE
==========

⏰ TIMESTAMPS
===========
0:00 Introduction
1:02 Recap of previous example
1:30 Two reports to track releases in Jira
2:12 The Version Report
7:27 The Release Burndown
12:52 Tips for releases running late
18:37 Conclusion

➡️ ONTO THE NEXT VIDEO!
=======================
Previous Videos in the Relative Estimation Series:

Playlists you might find helpful:

➡️ RELATED BLOG POST:
=====================

ℹ️ MORE ABOUT RICHARD & AXISAGILE APPS:
=======================================
Follow us on Instagram:

Connect with me on LinkedIn:

Learn more about AxisAgile Apps:

Learn more about AxisAgile:

Thanks for watching!

#scrum #agile #jira

[Heredia]

Hi Richard, thank you so much for your tips!!

[vasanthisaraswathi]

Adjust scope is perfect even I do the same.. Thanks and very useful tips

[OzanAktan-bn]

Hi, Richard! Your videos are very insightful. And, have lots of practical tips. I wanted to give a big shout out to your efforts in this channel!

I have a quick question regarding the product backlog grooming session. I want to refer to the example you have given in this video 11:18 So, there is already a 20 pointer in the product backlog. And, the team decides to split it into 5 equal sized items of 4 points. How do you do that with your teams in Jira to avoid this being reflected as additional work?

I assume that you are not adding 4 pointers as new items to the product backlog, right? Otherwise, they would be included to the Sprint Burndown chart and Product Backlog as additional work. Ideally, the total size of the Product Backlog should not change after the team breaks down the larger item into smaller items if there is no additional work. Of course, you can create subtasks for the 20 pointer. But, I don't think it would be an ideal solution since they are not subtasks, in real.

I would like to know how you get your teams to break down large sized items into smaller items in Jira. Finally, it would be really great to see a detailed video on product backlog grooming session with tips in Jira.


Thank you!
Ozan

[rahulraina.]

Hi Richard, Can you please let me know what's the difference between the Release Burndown Chart and Sprint Burndown Chart?

[gifss]

Can you make any video on ' how to handle spikes', do we need to estimate? where we need to track down the solutions for spikes??

[chrischelsisters]

Hi Richard, i can't see forecast and management reports, how can i enable ? pls reply Richard