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

Рет қаралды 81,617

Күн бұрын

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:
www.featurelibrary.com/
⏰ 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:
=============
Subscribe for more Agile and Jira videos! - / @axisagileapps
BLOG POST:
==========
bit.ly/38WBBIF
➡️ ONTO THE NEXT VIDEO!
=======================
How to perform Sprint Planning in Jira: • How to perform Sprint ...
🔗 MENTIONED LINKS:
===================
Download the sample data - bit.ly/39IhBdp
Declaring Product Backlog Bankruptcy - www.mountaingoatsoftware.com/...
Agile Backlog Tools - marketplace.atlassian.com/app...
Relative Estimation & Story Points - www.axisagile.com.au/blog/est...
Planning Poker - www.axisagile.com.au/blog/est...
ℹ️ MORE ABOUT RICHARD & AXISAGILE APPS:
=======================================
Follow us on Instagram:
/ axisagileapps
Connect with me on LinkedIn:
/ richardkaupins
Learn more about AxisAgile Apps:
bit.ly/3sfPwAm
Learn more about AxisAgile:
www.axisagile.com.au/
Thanks for watching!
#jira #agile #scrum

Пікірлер: 83

@lotionspotions3143 Жыл бұрын

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

@AxisAgileApps Жыл бұрын

It's a pleasure @lotionspotions3143! Thanks so much for your positive feedback 🙏😀

@parvathyviswanadh8142 2 жыл бұрын

Thank you! This was very helpful!

@AxisAgileApps 2 жыл бұрын

Thanks Parvathy! You are most welcome :)

@michellembok7805 Жыл бұрын

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

@AxisAgileApps Жыл бұрын

Our pleasure Michelle! Thanks for watching :)

@manuelahensman2071 Жыл бұрын

Great clear content to align teams!

@AxisAgileApps Жыл бұрын

Thanks Manuela!

@sayalidivekar29 2 жыл бұрын

Excellent video! Thank you. :)

@AxisAgileApps 2 жыл бұрын

You're very welcome! Thanks Sayali :)

@Nash0303 2 жыл бұрын

Your videos are fantastic!

@AxisAgileApps 2 жыл бұрын

Thanks Nash! :)

@gokfaromika955 2 жыл бұрын

Thanks a lot, really very useful!

@AxisAgileApps 2 жыл бұрын

Thanks Gok!

@onyekachukwuagu8861 Жыл бұрын

one of the best tutorial I have seen for free Amazing

@AxisAgileApps Жыл бұрын

Thanks Onyekachukwu! Really appreciate your feedback :)

@davidvonbank613 Жыл бұрын

Great video. Looking forward to more similar content.

@AxisAgileApps Жыл бұрын

Our pleasure David! Thanks for watching :)

@hxb6132 Жыл бұрын

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.

@AxisAgileApps Жыл бұрын

Very good point, thanks HB!

@BestHKisDLM 5 ай бұрын

Thank you!

@AxisAgileApps 5 ай бұрын

You're welcome! :)

@rohanpatil9692 2 жыл бұрын

Great work sir 🇮🇳

@AxisAgileApps 2 жыл бұрын

Thanks Rohan!

@klidraik 4 ай бұрын

Good video. Thanks.

@AxisAgileApps 4 ай бұрын

Many thanks!

@umeshchandgond6985 Жыл бұрын

Helped me alot

@AxisAgileApps Жыл бұрын

Thanks Umeshchand! Glad to hear it :)

@janangamalshan6236 2 жыл бұрын

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?

@AxisAgileApps 2 жыл бұрын

Good question Jananga. It's not always necessary to have all issues in the PB weighted with Story Points. The number of issues the team applies with Story Points depends on far ahead a Product Owner (PO) wants to forecast. For example, if my team had 50 issues in the Product Backlog, but the PO only wants a forecast for how long the top 20 will take (because those are what's included in the next release), then ideally the team would estimate those top 20 from the beginning. To answer the second question around Planning Poker, we use it to apply the initial estimates in the Product Backlog, but also subsequent estimates as the Product Backlog will change (items added, split, or updated). For more details on why we use Planning Poker, check out this blog article: www.axisagile.com.au/blog/estimation/planning-poker-at-pace/ If you would like me to clarify, or have more questions let me know :) Thanks! Richard :)

@phanik5986 2 жыл бұрын

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

@AxisAgileApps 2 жыл бұрын

Thanks Phani, at this point in time we’re focusing on Jira, but we might potentially branch out to other platforms in future.

@healthywithbenna 2 жыл бұрын

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 😊

@AxisAgileApps 2 жыл бұрын

Thanks Benna! I like the way you think :)

@healthywithbenna 2 жыл бұрын

@@AxisAgileApps you're welcome, I will binge watch tonight's. Starting my first scrum job on Monday and will welcome any new videos from you. I also subscribed

@AxisAgileApps 2 жыл бұрын

@@healthywithbenna Congratulations! If you need any advice we're here to help. You can connect with me on LinkedIn (just search for "Richard Kaupins") or feel free to email me at richard@axisagile.com

@abs3704 2 жыл бұрын

@@AxisAgileApps That's so generous of you. Thank you!

@AxisAgileApps 2 жыл бұрын

@@abs3704 Our pleasure! Thanks for checking out the channel :)

@coolreyno 2 жыл бұрын

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?

@AxisAgileApps 2 жыл бұрын

Hi Coolreyno, typically the Version field is not used for each Sprint, but for each release (i.e. when a Product Increment is delivered to the customer). It can be helpful for Product Owners to use this field to stay focused only on the features that are required for the upcoming release, and to avoid being distracted with what's going to be in the subsequent releases.

@rofkec Жыл бұрын

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.

@AxisAgileApps Жыл бұрын

Thanks for your support Lazar! And really appreciate the recommendation, we'll adjust our volume on subsequent videos.

@cemkocainan7330 Жыл бұрын

Thanks

@AxisAgileApps Жыл бұрын

Most welcome, thanks for watching!

@lukes5631 2 жыл бұрын

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

@AxisAgileApps 2 жыл бұрын

Hi Luke, thanks for pointing that out! My apologies for the confusion, when I say "description" filled out for the Product Backlog Item i'm implying a User Story with Acceptance Criteria has been added assuming you are using that format. Some teams don't use the User Story format that's why I used "description" as a more generic term.

@lukes5631 2 жыл бұрын

@@AxisAgileApps Appreciate the clarification. Also, as a young professional looking to transition into and master Agile and the Scrum framework, I'm really loving your content.

@AxisAgileApps 2 жыл бұрын

@@lukes5631 That's awesome to hear. Thanks Luke :)

@mvsprasanna2656 Жыл бұрын

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.

@AxisAgileApps Жыл бұрын

Hey @mvsprasanna2656, not sure if you saw my reply to your earlier message? The items are estimated by the developers after discussing it with the PO. Most teams will use Planning Poker to do this. Hope it helps and let me know if you have any other questions. Thanks again!

@coolreyno 2 жыл бұрын

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

@AxisAgileApps 2 жыл бұрын

Hi Coolreyno, thanks for your questions. Jira only allows you to add a single flag to a Product Backlog item.

@mvsprasanna2656 Жыл бұрын

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

@AxisAgileApps Жыл бұрын

Hi Mvs Prasanna, good questions. Refining the Product Backlog should be done before Sprint Planning. Typically the Product Owner will organise "Product Backlog refinement" workshops during the Sprint to prepare for the upcoming Sprint. When it comes to the active players, most Scrum teams start by having everyone involved. I.e. the Product Owner will invite the entire development team to discuss and refine the upcoming Product Backlog items. That said, it's not mandatory to have everyone involved, and some Product Owners will decide to only invite a subset of the team if it makes sense to do so. Hope it helps, and let me know if you would like me to clarify further. Thanks for watching! Richard

@JaroslavJasek24 Жыл бұрын

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

@AxisAgileApps Жыл бұрын

Hi Jaroslav, sorry about the delayed reply. I suspect you may be using a "Team Managed" project, in which case Board Settings are not available. When creating a project, you'll need to select "Company Managed" and use the Scrum template. Cheers, Richard

@subhasundar9881 Жыл бұрын

Hi, Do you have any whatsapp group for Agile and Scrum aspirants? thanks.

@AxisAgileApps Жыл бұрын

Hi Subha, sorry we don't have a WhatsApp group at this time.

@tusharparmar7142 Жыл бұрын

Which of these five "sprint-ready" are searchable in Jira?

@AxisAgileApps Жыл бұрын

Hey Tushar, great question. Technically all of them are searchable using Jira's JQL syntax.

@PMulti 2 жыл бұрын

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

@AxisAgileApps 2 жыл бұрын

Hey Samuel, it depends on what your team means by "parking lot". It's often used as a term for items that need further discussion - if that's the case for your team, there are many ways to capture it in Jira but the most common would be to create a Product Backlog Item and use a label or workflow status to indicate it is in the "parking lot". Alternatively, if it is work that needs to be completed within the Sprint, I like to have a "blocked" column on the Active Sprint Board. And any items that need further discussion (i.e. are in the parking lot) will be placed in the blocked column until that discussion takes place. Hope that helps, I'll be creating videos related to this in future.

@PMulti 2 жыл бұрын

Thanks for your reply, what I actually mean is for instance during daily standup if a team member is giving too many details the scrum master often says can we more this to the parking lot so I am trying to understand where this parking lot is in Jira or confluence

@flawlessgoldenhair2006 Жыл бұрын

@@PMulti when they say they we at to move a discussion to the parking lot it means after the standup meeting you and that person will stay behind n talk more about that specific ticket on the Jira board, be it a bug or blocker…I hope this helps

@temitopekade590 Жыл бұрын

@Samuel, it means something to be discussed further after the time boxed DS. Meaning the people involved can stay back after the initial 15 mins.

@temitopekade590 Жыл бұрын

So the parking lot is just a term used. It's neither in Jira or Confluence. It is an a location in the mind !

@AnhMinh-sm7uc Жыл бұрын

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

@AxisAgileApps Жыл бұрын

Hi Anh Minh, great question. My preference is to keep it simple and go with your first option: Put it back in the Product Backlog, and then add it to a future Sprint. At Sprint Planning, ask the team to re-evaluate the un-finished sub-tasks on the Product Backlog item, and adjust them. This might mean adding new-sub tasks, deleting sub-tasks, or changing the status of existing sub-tasks. Does that make sense? - Richard

@AnhMinh-sm7uc Жыл бұрын

@@AxisAgileApps Thats make sense! Thanks for your advise

@rakeshsekhri454 Жыл бұрын

Please correct the following understanding: 1. Product Backlog is created by the PO and the SM 2. Product refinement is performed by PO,SM & team (may include subject matter experts etc) this includes story estimates (hrs or story points etc), priority and sufficient detail - DEEP 3. Sprint Planning by PO, SM & team using JIRI The video does not talk about how much time these items take - should we create a Sprint 0 to do this or should it be included in the Sprint 1 timeline?

@AxisAgileApps Жыл бұрын

Hi Rakesh, sorry about the late reply. In response to your questions: 1. The PO is primarily the owner of the Product Backlog, but may have others help in establishing and maintaining it. For example Business Analysts, Technical Experts, Subject Matter Experts etc. 2. That is correct, however it is up to the PO to decide who needs to be present for Product Backlog Refinement. Some PO's only include a subset of the Delivery team which can be fine. 3. Correct, please check out my other videos on how to perform Sprint Planning with Jira :) And lastly, good pickup, yes I didn't mention how much time it take to prepare the Product Backlog (and other details) before the first Sprint. This is because it largely depends on the size and complexity of your project. A small project may only require a few days to prepare the Product Backlog before Sprint 1, while larger projects can require many months. For this reason, I prefer not to call this Sprint 0, as it implies that all the preparation work can be done within a single Sprint which may not be the case. Hope it helps and let me know if you have any other questions, and thanks for watching! :) Richard

@PMulti 2 жыл бұрын

Samuel Chukwu

@AxisAgileApps 2 жыл бұрын

Hey Samuel, did you have a question about this video? All I can see is your name in the comment above. Let me know! :) Richard

@PMulti 2 жыл бұрын

Yes brother I do I have the question above

@toby9999 Жыл бұрын

Personally, I find Jira and the other so called "productivity tools" to be my biggest time waster. One get's to the point where the tools get in the way of the job. Even something as simple as searching in Jira is not simple at all. The Jira search language is a friggin nightmare. So frustrating. Even the Jira GUI is atrocious. Not a fan of the scatter gun design.

@AxisAgileApps Жыл бұрын

Hi Toby, you're not alone. We work with many teams that share your frustration and it's part of the reason we create these videos :)

@dustinbutler3554 2 жыл бұрын

Please move faster

@AxisAgileApps 2 жыл бұрын

Hi Dustin, thanks for the feedback. If you mean move the content faster a tip is to adjust the playback speed in KZfaq. If you mean produce more content faster, we’re on it ;)

@showneath 2 жыл бұрын

Brilliant content. The pacing is perfect. We can always adjust the speed if we like.