How to Estimate a User Story with Story Points in Jira | Atlassian Jira

preview_player
Показать описание
In this #Atlassian #Jira video you are going to learn how I determine the value of story points. This is a topic that has many opinions. How do you value story points? Finding information on how to estimate in agile/scrum is really challenging. There's a lot of information on the theory of how you should estimate and/or use story points, but very people actually share how to do it in a large organization. If you've been struggling to figure out how you should be using story points, this video is perfect for you. My technique might not align with #agile best practices, but I've been using this method for a few years now and it works for my teams. By accounting for complexity and time, teams can more reliably estimate their work and provide greater visibility to the organization.

If you haven't already, I recommend you check out my previous videos where I discuss the value of using Story Points to help your team estimate their work for the sprint ahead.

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
Рекомендации по теме
Комментарии
Автор

You indeed knew your kraft. Full respect to you. Unique👏

benjomoreno
Автор

Just discovered your videos. You're the best man. Clear, strait to the point, well presented, clearly backed by a long experience. Happily learning from you. This is my #1 go to channel for everything SCRUM/JIRA. I hope you'll continue.

KachWahedTM
Автор

it is great! it helped me as a Scrum master a lot. thank you for this video!

SamratSinha-egjg
Автор

Yes yes yes! Everything Ahmed said. Please keep them coming😁

staciejohnson
Автор

Thank you. We don't use story points because of the time estimating. Then turn around and use sprints but question why we can't plan accordingly. I'm now a product owner and am going to be readdressing this topic again using your t-shirt size example.

michaelc
Автор

Wow, It's fantastic bro I am so confused about this story's points now my confusion is gone thanks Man you are such an excellent teacher.🤗🤗🤗

syedosama
Автор

Thank you, really helps grasp story point estimates

michaelchifulo
Автор

Hi Alex, Lets say we have a 21 point story, would you break the story and assign to different people or the same person? secondly would you combine development and testing hours in the overall story point even if it needs to be performed by two different individuals?

vikrama
Автор

Apologies if I missed this on the video, but in the case where you have the process Develop -> Review -> QA, should the story point estimate represent completing all these stages, or just the Develop stage?

JoePrivett-crnp
Автор

Is the approximate story points specified for a two week sprint? or is it irrespective of the duration of the sprint?

allavudeens
Автор

Murphy's law 😉

Totally agree... upwards of 10 points means break it down.

markgemmell
Автор

Do you have any somewhat real world examples of breaking down the 8/13/21 SP tasks into smaller tasks? It would be great to see some good and bad examples. Also, when you coach teams, do you even allow 8 SP or higher tasks to make it into the sprint? or do you tackle this in the Product Backlog refinement and break down the tasks with the team there into 5 SP or less tasks?

darrenweir
Автор

Hi sir,I am newbie scrum master and really struggling on how to coach my team to provide storypoint,your videos are always very helpful to me,can you help me with this question:usually who will be the one estimate storypoint for a story? how about to have developer to create subtasks and provide storypoint accordingly after grooming session?so I can see sum story point on parent story,please advice, thanks a lot

tinazhuang
Автор

Hey, video looks cool and simple. One quick query: duration is in man days and not scrum team days. Plz clarify

sanjayjena
Автор

Ideal Gas Law. I think that's the law you're referring to. :)

ATRoss-pwue
Автор

bro this has got to be the worst business name / youtube channel name ever.. you should look into changing it.

novanoskillz