How to Plan the PERFECT Sprint - Atlassian Jira Software

preview_player
Показать описание
Planning a sprint in Jira can be a little tricky. This video walks you through how I typically plan a sprint for a SCRUM team. If you are a scrum master wondering how to plan a sprint, this video is full of helpful tips that you can start leveraging immediately. These are all tactics that I have used over the last six years and have seen great results. If you have been wondering how to plan the perfect sprint, or if you just want to see how others do it, check this video out. I'll show you all the techniques that I use when planning out sprints with my teams. Set up your team for success and properly plan out your team sprints.

Learning the basics here can really help you down the road. Knowing how to find the information that is most critical to you and being savvy on where things are contained within the world of Jira are going to give you an edge over your teammates.

If you like this video, please make sure to give it a thumbs up. If you haven't already, please consider subscribing. If you have any questions about anything discussed so far, please feel free to make sure you leave your question in the comments section.

Jira Merch:

Link to my other Atlassian Jira videos

Link to my Atlassian Live Streams:

Link to Atlassian's Jira products:

Link to my Fiverr profile:

Link to my Upwork profile:

Link to my personal website
Рекомендации по теме
Комментарии
Автор

I agree 100% about assigning stories to people; accountability says it all. Thanks very much. Kate H.

katehanson
Автор

Totally agree. Orphaned stories suggest unstructured work. Epics help to understand purpose. Dependencies between tasks are also almost always present in coding and worth capturing for planning a sprint. It's a shame people push back on these obvious realities of real projects.

markgemmell
Автор

I loved this video as I recently joined an org with my first ever senior role as a QA Lead. Great suggestions!

adarshsingh
Автор

Hi, good video. I would just comment on a few "non pure agile" points you mentioned, which I think are perfectly aligned with agile and more precisely scrum.

- Epics - scrum doesn't say anything about stories, epics or tickets per se. It mentions items, and purposely leaves it vague. Most agile SW dev process in the world will probably try to build something that will take more than one sprint to get to the point of stopping further development. As such, it is obvious stories are tied together. Epics (or features in AZ devops) are just a context. Context is information. Information is good. Completely agile and scrum supported, as long as you don't misuse it like setting in stone a scope (stories inside) of epic, or track actual vs planned.

- assigning stories to developers - scrum guide again doesn't say anything about such a thing, but it does mention that sprint backlog is items+plan. Plan is who and when does something --> assignment is completely fine for pure scrum, as long as you don't do it prior to sprint planning. If your point is that story shouldnt be assigned, but subtask should, again, scrum guide doesn't say anything about stories, tasks, subtasks. Just a plan, and you do a plan in a way best fitting your situation.

gogothegogo
Автор

How do you deal with situations where some people have a higher capacity and others have a significantly lower capacity. How does that impact the team? This was amazing. Going to watch the rest of your videos. Very helpful and practical for a starting scrum master.

ON-zqny
Автор

Another great video! You mentioned that you were going to make videos about velocity/capacity and estimation. Are they out yet? Thanks!

jasminefrancis
Автор

what you say about accountability sounds about right

zambchi
Автор

Great video. Thanks. One question, who populate the epic and stories? Scrum Master or Product Owner?

SydneyUgbeda
Автор

how do you show the performance of the team in a graph view

lalithamitte
Автор

If you assign stories to different members, you are maximizing work in progress, increasing lead times, reducing quality, reducing collaboration, and creating silos. You know how to use the tool, but have completely missed whole point of Agile.

malbrantj
Автор

do you teach azure devOps for scrum master?? also as you are jira expert can you help me understand - i just certified as a scrum master, want to get some hands on as a scrum master, is jira that is practised everywhere or do i need to know more tools and do you or can you train me and what are your charges?? thanks

anahash