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:
bit.ly/46f6PE8
🔔 SUBSCRIBE
==========
Subscribe for more Agile and Jira videos! / @axisagileapps
⏰ 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:
Part 1 - What are Story Points? • What are Story Points ...
Part 2 - What is Planning Poker? • What is Planning Poker...
Part 3 - What is Velocity? • What is Velocity and h...
Part 4 - Release Planning in Jira • Release Planning in Ji...
Playlists you might find helpful:
Overview of Jira and Scrum playlist: • How to use Jira and Co...
Product Backlog video playlist: • Establishing your Prod...
Sprint Planning video playlist: • How to facilitate Spri...
➡️ RELATED BLOG POST:
=====================
axisagileapps.com/essential-r...
ℹ️ MORE ABOUT RICHARD & AXISAGILE APPS:
=======================================
Follow us on Instagram:
/ axisagileapps
Connect with me on LinkedIn:
/ richardkaupins
Learn more about AxisAgile Apps:
axisagileapps.com/
Learn more about AxisAgile:
www.axisagile.com.au/
Thanks for watching!
#scrum #agile #jira

[@Heredia1973]

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

[@AxisAgileApps]

Thanks Randall! it's our pleasure :)

[@vasanthisaraswathi]

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

[@AxisAgileApps]

Thanks Vasanthi! Our pleasure :)

[@gifss99]

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??

[@AxisAgileApps]

Hi there, thanks for the suggestion. I've added it to our video backlog. So you don't have to wait the way I handle spikes is by time-boxing them. After the developers have decided and agreed on a time-box for the spike with the Product Owner, they will typically have an idea of the Story Points to allocate.
What's important is for the developers to let the Product Owner know if more than the allocated time is required to complete a spike after they have started it's implementation. If more time is required than the developers will need to make sure that the Product Owner is happy to proceed.
Hope it helps and let me know if you have any other questions.
Thanks!
Richard

[@user-vd7rp4wy1o]

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

[@AxisAgileApps]

Hi Ozan, firstly apologies on the delay in reply. Great questions. I like to use Jira's splitting feature to break down larger Product Backlog items. You can access the splitting feature by right-clicking on the Product Backlog item and you'll see "Split issue" as an option in the context menu.
Unfortunately what Jira will do is then create new Product Backlog items, and yes, that means they are represented as "Work added" on the Release Burndown because they have been added to the release after the release start date.
And thanks for your suggestion for a detailed video on Product Backlog grooming. I'll add that one to our Video Backlog :)
Thanks!
Richard

[@chrischelsisters5558]

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

[@AxisAgileApps]

Hi there! Do you see "Reports" in the left panel? If not you might be using a "Team Managed" project. If that's the case you'll need to click on project settings at the bottom of the left panel, and then click on "Features" and enable reports. That said, keep in mind that the Release Burndown and Version Report are unfortunately not available with Team Managed projects.