Get your Product Backlog in Jira right! | Jira Tips & Tricks from the Agile Experts

preview_player
Показать описание
In this video you will learn what makes a good Product Backlog in Jira, including:
- The DEEP acronym to help remember the attributes of a good Product Backlog
- What details to include in your Product Backlog items
- What are 'epics' in the context of Jira and how to use them
- How far ahead you should refine Product Backlog items
- How to indicate items as 'Sprint-ready'

👉 MASTER AGILE REQUIREMENTS
==============================
Master Agile Requirements with our latest product, the "Feature Library" and accompanying Mastering Agile Requirements online course. For more information click on the link below:

⏰ TIMESTAMPS:
===============
0:00 How to get your Jira Product Backlog right
0:49 The DEEP acronym
4:44 'Epics' in Jira
7:25 How far ahead to refine Product Backlog items?
7:51 What detail should we add?
9:35 Attaching more information
10:35 Applying an estimate
11:51 Assigning and using a version
14:20 What are 'Sprint Ready' Product Backlog items?
14:57 How to indicate 'Sprint Ready' Product Backlog items?
15:05 Option 1 - Using the 'Sprint' feature
17:10 Option 2 - Using the 'Flag' feature
18:07 Option 3 - Using the 'Labels' field
19:42 Option 4 - Setting a card color
21:35 Option 5 - Using a workflow status
26:08 How to deal with a long Product Backlog

🔔 SUBSCRIBE:
=============

BLOG POST:
==========

➡️ ONTO THE NEXT VIDEO!
=======================

🔗 MENTIONED LINKS:
===================

ℹ️ 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!

#jira #agile #scrum
Рекомендации по теме
Комментарии
Автор

one of the best tutorial I have seen for free Amazing

onyekachukwuagu
Автор

This content is enormously helpful!! Thank you so much! ❤

lotionspotions
Автор

Good aussie quality, thanks! One observation, the "card colour' option for sprint ready items only works when you have created the associated label, this means you have both a label reading 'Sprint ready' as well as a card colour indicating a 'sprint ready' status, a bit of duplication. The customization of the workflow is best in my view. Keep up the good work, Richard.

hxb
Автор

Thanks for the video. 1 question: What about if we received a bug (new) so we need to add in some EPIC or add a task (type bug)?

How to handle the bugs in current sprint and in product backlog?

Salmanmushtaq-csjm
Автор

This was extremely helpful! It helped me to understand Product backlog refinement a little bit more. Thank you!

michellembok
Автор

@13:44 In the PB refinement summary, I noticed that you didn't cover any "acceptance criteria" in order for a PB Item to be defined as Sprint Ready. Was it intentionally left out?

lukes
Автор

Amazing tutorial. Although, I have a question. Should all the issues in PB be weighted with storypoints right from the beginning? If that's the case, why do we use something like planning poker?

janangamalshan
Автор

Thanks for the video. Can you do all these planning, refining for Rally software as well

phanik
Автор

Great video. Looking forward to more similar content.

davidvonbank
Автор

Thank you for a great content. You got a sub from me and a like on all your videos!

One recommendation: Raise your volume up a little bit. When I have music turned on in the background, your voice is too low, indicating that baseline sound volume on your videos is lower than for others.

rofkec
Автор

Hi Richard,

Who will estimate the product backlog items? Is it estimated by PO after he/she discuss and refine the product backlog items with entire development team.

mvsprasanna
Автор

Thanks, How I can tell if issue belong to Backlog ? I work with Jira data import/API and trying to find clear criteria how to set switch for Jira issues Backlog_YN

mario-t
Автор

Whats the difference between subtask and child issues ?

prasadc-icjc
Автор

Thanks for the video.
So do you mean you can use Version#1 to call for 1st sprint and Version#2 for the following sprint and so forth?

coolreyno
Автор

Who are the active players while doing these? Is this to be done within the sprint planning or prior to it?

mvsprasanna
Автор

Can you add more that one flag on an issue?
If yes I assume you can change a flag color?

coolreyno
Автор

I love this video, I'll just stick to the 1st or second way because it is easy and I love easy stuff. Thank you 😊

healthywithbenna
Автор

Hello - why I have not Board setting in my Backlog ?
I use Free version - this is a reason ?

JaroslavJasek
Автор

I have problem that:
Adding subtask into story and put it in Sprint
1 Sprint have 2-3 story and already have subtask (estimated) on it
In the end of sprint, I have 1 story that not done yet: example 2 subtask not done
So what should i do next?
1. Put it back to Backlog and pick story to the next sprint, in the next sprint sub task wil be continue as their status on the previous story
2. Move all sub task to done, put back to backlog, on the next sprint re estimate the story to see which sub task need to do
3. Re-oganize story, create task and relate it to story, at the end of sprint, put all the task to done and see if story done or not. If story not done, re estimate it with creating new task related to them
Please help! thanks for any advise

AnhMinh-smuc
Автор

I hear people talk about parking lot during daily standup so my question is where is this parking lot in Jira and how do you create one

PMulti