Release Planning in Jira - Managing Projects with Jira

#ReleasePlanning #Agile #productdevelopment #productbacklog
Here we explore the release planning feature of Jira.
For Program Related Queries email - [e-mail] / Call or WhatsApp Us [phone]
Follow us on -
LinkedIn - / izenbridge-consultancy...
Instagram - / izenbridgeofficial

[@priyankar3532]

Such a clear explanation for each step. Thanks Saket Sir

[@izenbridge]

Thank you.

[@mynameisjimmy9823]

You mentioned product backlog, can we use sprint backlog instead of that?

[@jasper5016]

Is this the same release planning that Release Manager does? Also, can you please cover more about release manager responsibilities?

[@izenbridge]

Release Manager job in my observations defined differently in many organization , but in general release manager is more attached to managing configuration and technical part of release.

[@mittonitto1234]

I have questions. How do you answer this. What do you do as a scrum master on backlog refinement in practical.
. What is the data you're using in the organization.
Please answer me.

[@izenbridge]

For refinement, there should be DOR which has a checklist. If stories are following the checklist of DOR. then we can say stories are refined enough to be picked and follow the INVEST principle. Some other ground rules can be made like the story should be small enough so that it is completed within the iteration of a sprint.

[@sweekrutysenapaty4472]

Hi Saket, I have one question, I have attached versions to a couple of issues by drag and drop but when I am clicking on details and getting navigated to the "Releases" screen, no. of issues is showing 0 while under version the details are showing correctly, Is there any configuration needs to be done from my side please explain

[@izenbridge]

So, I hope you have created the release and selected the release under the fixed version at the story or task level(standard issues). After this under-release detail, those issues should come as a count. I am assuming you have done all these on cloud version of Jira.

[@babalolamuyizz127]

So if the Product owner can use version to set up Release plan, modify Release scope & initiate Release, then why do we need a Release manager?

[@izenbridge]

For these things, permission can be configured. And moreover, Jira maintains history every in and out. So that will not be easy for anyone to change the scope

[@abhiraj7150]

Why is Prateek Kuhad giving a Jira Training?