How to perform Sprint Planning with Jira - Part 1 | Jira Tips & Tricks from the Agile Experts

Рет қаралды 144,589

Күн бұрын

In this first video on Sprint Planning in Jira, we cover:
- What needs to be determined at Sprint Planning
- How to prepare for the session
- How to setup a Sprint in Jira
👉 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 Start
1:11 Overview of Sprint Planning
2:58 What to prepare
6:18 Sprint setup in Jira
7:45 Choosing a Sprint name
9:05 Deciding on a Sprint length
10:28 Adding a Sprint Goal
➡️ ONTO THE NEXT VIDEO!
=======================
How to perform Sprint Planning with Jira - Part 2: Using Story Points, Velocity: • How to perform Sprint ...
How to perform Sprint Planning with Jira - Part 3: Using time and sub-tasks:
• How to perform Sprint ...
BLOG POST
==========
bit.ly/37qhqTm
🔔 SUBSCRIBE
============
Subscribe for more Agile and Jira videos! / @axisagileapps
🔗 MENTIONED LINKS
===================
The 'Sprint Ready' term, and the Product Backlog - • Get your Product Backl...
1 on 1 Car Rental Sample Data for Jira - • Kick-start your Jira P...
ℹ️ 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

Пікірлер: 77

@richardhayden5409 Жыл бұрын

I've previously used pizza toppings as sprint names, like Margherita for sprint 1, laying out the most basic stuff, going through increasingly more complex topping styles until we hit a full year of dev marked by quattro stagioni, and finally landing on calzone ("It's a wrap!") for when we finished the work entirely and moved onto something else. That generally amused people (and caused a few light-hearted arguments about what should and should not be considered a pizza topping).

@AxisAgileApps Жыл бұрын

Hahaha love it!

@jakewu9916 2 жыл бұрын

Thank you, Richard. This is the best YT video on planning with Jira! Looking forward to see the next part of the series!

@AxisAgileApps 2 жыл бұрын

Thanks Jake! Glad you enjoyed it, there's plenty to come :)

@AxisAgileApps 2 жыл бұрын

Thanks again for the feedback and watching the channel Jake. Just letting you know both the second and third parts of this series have been published. All the best!

@bhlmmfm6592 2 жыл бұрын

@@AxisAgileApps love d video

@AxisAgileApps 2 жыл бұрын

@@bhlmmfm6592 Thank you!! :)

@Unicorn-cl7fw 2 жыл бұрын

Thank you for the quality content. Looking forward to new videos 😊

@AxisAgileApps 2 жыл бұрын

Thanks Uni corn, next one is almost ready :)

@laurie808 2 жыл бұрын

Excellent!

@AxisAgileApps 2 жыл бұрын

Thanks Laura! :)

@nduka_vic 7 ай бұрын

Thank you so much for the value you give

@AxisAgileApps 7 ай бұрын

Thanks Victor! It's a pleasure :)

@rushmidesai Жыл бұрын

Great content..waiting for more. Thanks

@AxisAgileApps Жыл бұрын

Thanks Rashmi, more to come! :)

@otegaotega4908 2 жыл бұрын

Thanks for the amazing content

@AxisAgileApps 2 жыл бұрын

Our pleasure Otega Otega, thanks!

@hamzahinusah9972 2 жыл бұрын

Thanks for this insightful video

@AxisAgileApps 2 жыл бұрын

Thanks Hamzah!

@andresantos1889 Жыл бұрын

Awesome content, thanks from Brazil.

@AxisAgileApps Жыл бұрын

Our pleasure Andre! And thanks for watching :)

@anandanm2336 11 ай бұрын

Thanks for sharing your knowledge 😊

@AxisAgileApps 11 ай бұрын

Thanks again @anandanm2336!!

@valt2305 Жыл бұрын

Best video

@AxisAgileApps Жыл бұрын

Thanks Val!

@healthywithbenna 2 жыл бұрын

Awesome content, please share more. Thank you 😊

@AxisAgileApps 2 жыл бұрын

Thanks Benna, more is on the way :)

@sreevibes143 2 жыл бұрын

Awesome explanation

@AxisAgileApps 2 жыл бұрын

Thanks Sridevi!

@kamonthipme89108 Жыл бұрын

thank you so much

@AxisAgileApps Жыл бұрын

My pleasure! thanks for watching :)

@omerhatim4326 Жыл бұрын

Thanks

@AxisAgileApps Жыл бұрын

Thanks Abu Kenan! You are welcome :)

@ranitajain2437 2 жыл бұрын

Waiting for the second part

@AxisAgileApps 2 жыл бұрын

It’s coming soon! :)

@AxisAgileApps 2 жыл бұрын

Second and third part have been published :) thanks for checking out the channel Ranita!

@aks18sep Жыл бұрын

Thanks Axis

@AxisAgileApps Жыл бұрын

Our pleasure Ashish! :)

@melodynorsworthy Жыл бұрын

Rivers in Texas were used as Sprint Names.

@AxisAgileApps Жыл бұрын

Nice one Melody!

@rolemodel99 2 жыл бұрын

What might you suggest to teams that also work with product goals? How might they represent it in Jira?

@AxisAgileApps 2 жыл бұрын

Hi Rolemodel99, Product Goals are typically long term objectives that can span potentially multiple releases. For this reason I find the best place to document a Product Goal is not in Jira, but in Confluence (or other knowledge management system of your choice). Confluence is particularly useful because it easily integrates with Jira, allowing you to document high-level business objectives (for reference) and relate them to Jira issues (for tracking). So in other words, Confluence allows a team to see the long-term objective (Product Goal), and how it may have been broken down into releases in Jira, and how each release has been broken down into a Product Backlog.

@reelandlifetruth1 6 ай бұрын

Sprint name - Light.

@AxisAgileApps 6 ай бұрын

Thanks for sharing! :)

@sreevibes143 2 жыл бұрын

Can you explain about sprint retrospective and sprint review

@AxisAgileApps 2 жыл бұрын

Hey Sridevi, certainly. We’ll be covering the Sprint Review and Sprint Retrospective in upcoming videos.

@janangamalshan6236 2 жыл бұрын

Another amazing video. Shoutout from Sri Lanka 🇱🇰 Can the sprint durations differ from one another in the same project?

@AxisAgileApps 2 жыл бұрын

Hi Jananga! My preference is not to vary Sprint durations within the same project as it will make your team's Velocity inconsistent (assuming your measuring Velocity), secondly it can upset the teams rhythm, and thirdly it does make it more difficult for Stakeholders to attend the Sprint Review as it moves around in their calendars, and stakeholders typically have very busy calendars so they may end up not attending. The only time I typically suggest changing a Sprint duration is when a team is just starting off with Scrum, and they're trying to find a Sprint length that is right for them. But once they find that Sprint length, it's best to stick with it :)

@janangamalshan6236 2 жыл бұрын

@@AxisAgileApps Understood. Thanks!!

@AxisAgileApps 2 жыл бұрын

@@janangamalshan6236 Our pleasure! :)

@kargeo78352 10 ай бұрын

such amazing presentation and detailed explanation, our sprint name is Coffee, Tea, and sometime Ferrari

@AxisAgileApps 10 ай бұрын

Thanks Karzan! And love the Sprint names :)

@rolemodel99 2 жыл бұрын

what is the thinking around adding the sprint goal last? what happens to behaviours of the team when this is added last?

@AxisAgileApps 2 жыл бұрын

Hi Rolemodel99, another good question. A team will only decide on a Sprint Goal towards the end of Sprint Planning if it's dependant upon what they forecast can get done. What's common is for Product Owners to suggest an ideal Sprint Goal at the beginning, but for teams to confirm what's possible at the end. If the ideal Sprint Goal is not achievable, then the Product Owner and delivery team discuss and come to an agreement as to what's more realistic.

@rolemodel99 2 жыл бұрын

only two options (velocity+story points, time)? what are your thoughts on using throughput?

@AxisAgileApps 2 жыл бұрын

Hi Rolemodel99, good question! When you say throughput I'm assuming you mean average number of Product Backlog items a team completes per Sprint. I have seen teams do this and it can certainly work. For it to work well requires the team to split their Product Backlog items so that they are all uniform in size. I also suggest that the size of those items is relatively small allowing for greater precision. It is fairly rare to see teams be able to do this and that's why I didn't mention it, but perhaps it will be an additional video in this series ;) Thanks again for the question and I hope my response helps!

@PMulti 2 жыл бұрын

Good afternoon brother, please where do you create sprint calendar? Is it in Jira or confluence and how please

@AxisAgileApps 2 жыл бұрын

Hey Samuel, when you say a Sprint calendar, do you mean when your Scrum activities will be scheduled? If so, Confluence is the best place to document that information and share with your team.

@MuhammadAtif-pn9ox Жыл бұрын

If you are using and Sprint and Fix Versions both then how do you manage things in Jira? Do you release version upon Sprint completion or regardless of Sprint end you can release a version in between?

@AxisAgileApps Жыл бұрын

Hi Muhammad Atif, good question. You can release regardless of Sprint end. Some teams will release multiple times per Sprint, others will release after many Sprints. You can look at Sprints as to help the team regularly inspect and adapt, and does not dictate release cycles. Hope it helps! Richard

@SH-vo8ih Жыл бұрын

Good presentation, but too many references to other videos, please keep every video complete in itself. Thanks

@AxisAgileApps Жыл бұрын

Thanks S H! Your feedback is much appreciated and has been noted :)

@erhkpage6864 Жыл бұрын

WHEN (in which event) do team determine thier capacity?

@AxisAgileApps Жыл бұрын

Hi @erhkpage6864 sorry for the late reply. I typically like the team to work this out by sending around a spreadsheet as I've shown in the third video in this series (kzfaq.info/get/bejne/b5qjpL2SybGzdn0.html&lc=UgyGn9Yj-65FZTXafNt4AaABAg). Some teams will also do it at the start of Sprint Planning, but I like to hit the ground running with it already prepared :)

@Velocity0428 Ай бұрын

Why don't I have a "Start Sprint" button like you do?

@AxisAgileApps 7 күн бұрын

It's most likely you don't have the right user permissions to start a Sprint, or you might not be using the "Scrum" project template.

@MichaLipek Жыл бұрын

Instead of story points or hours, you can just take a certain number of PBIs to a new sprint. Estimations are usually just guesses anyway and in most of the cases developers don't know how much time the story will take. Personally. I would also stop using Jira as it doesn't help with anything.

@AxisAgileApps Жыл бұрын

Thanks Michal, good points. If you go with the number of PBIs just make sure your team breaks the PBIs down so their relatively small and of similar size. Appreciate the thoughts!

@sebastianzelechowski8557 9 ай бұрын

My managers don't really like anything original. Sprint 20/10/2023 are used.

@AxisAgileApps 9 ай бұрын

Thanks for sharing Sebastian!

@techlearn2642 Жыл бұрын

Hi there is no connection with this video and next video. where are the middle steps?

@AxisAgileApps Жыл бұрын

Hi there, sorry for the confusion. This first video shows how to setup a Sprint in Jira, and next video (kzfaq.info/get/bejne/mNx7d8-VuM6paHU.html) shows how to add items to the Sprint to create a Sprint Plan. Let me know which steps are unclear and I'll clarify. In any case, thanks for watching :)

@pmanification Жыл бұрын

Literally had to 1.5x this video

@AxisAgileApps Жыл бұрын

hah thanks @pmanification that's a great tip for all those who find the video too slow. I have tried to speed up my delivery in future videos :)

@foxyfox7961 Жыл бұрын

Hard to watch that waving hands

@AxisAgileApps Жыл бұрын

Thanks for the feedback Foxy! Perhaps I get a little too passionate about Agile and Jira ;) but appreciate the feedback and I have been told to limit the hand waving by our team here so you will notice it reduce in future videos.

@CVenture 11 күн бұрын

You duuummbassss