How to Estimate a User Story with Story Points in Jira

No video

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

Рет қаралды 8,864

Күн бұрын

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:
linkpop.com/ap...
Link to my other Atlassian Jira videos
• Jira Tutorials
Link to my Atlassian Live Streams:
• Jira Community Live St...
Link to Atlassian's Jira products:
www.atlassian....
Link to my Fiverr profile:
www.fiverr.com...
Link to my Upwork profile:
www.upwork.com...
Link to my personal website
www.apetech.me/

Пікірлер: 29

@ApetechTechTutorials 2 ай бұрын

To get more resources and get in contact with me check out this link linktr.ee/apetech

@benjomoreno1391 Ай бұрын

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

@staciejohnson9578 Жыл бұрын

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

@ApetechTechTutorials Жыл бұрын

Thanks for the positive feedback!!!! I'll keep them coming.

@KachWahedTM Жыл бұрын

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.

@ApetechTechTutorials Жыл бұрын

Thanks!! Means so much that it's helping you out!!

@SamratSinha-eg5jg 2 ай бұрын

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

@syedosama4353 Жыл бұрын

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.🤗🤗🤗

@ApetechTechTutorials Жыл бұрын

Thank you so much!! Comments like this give me the energy and motivation to keep on going!

@michaelc5168 9 ай бұрын

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.

@ApetechTechTutorials 8 ай бұрын

Glad I was able to inspire!

@JatinBatra-pj7kl Жыл бұрын

That back wall is inspiring.

@michaelchifulo4696 Жыл бұрын

Thank you,really helps grasp story point estimates

@nwumforjames8312 Жыл бұрын

Great job 👍 THANK YOU!

@ApetechTechTutorials Жыл бұрын

Thank you for watching! Hope it was beneficial to you!

@vikrama2189 Жыл бұрын

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?

@JoePrivett-cr5np Жыл бұрын

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?

@ApetechTechTutorials Жыл бұрын

My philosophy is that the story points should reflect the work of the person providing the estimate. That to me means only the development work.

@allavudeens 7 ай бұрын

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

@markgemmell3769 10 ай бұрын

Murphy's law 😉 Totally agree... upwards of 10 points means break it down.

@tinazhuang8973 Жыл бұрын

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

@ApetechTechTutorials Жыл бұрын

The developer should ALWAYS estimate the Story. The Developer can create subtasks, estimate those, and then roll them up to the Story. Problem is that you don't see the subtasks in the backlog . . so, it makes it a little harder to use.

@darrenweir2504 Жыл бұрын

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?

@ApetechTechTutorials Жыл бұрын

Excellent feedback! I'll make a video on this!

@sanjayjena984 2 жыл бұрын

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

@ApetechTechTutorials 2 жыл бұрын

If you are going to use man days, I recommend you change your settings to use Original Estimate instead of story points. This will help you track hours/days easier.