How To Estimate User Stories? | #9

It's time to Estimate User Stories in the Story Map we created in the last video.

But, what about #NoEstimates

In this video, I will

#Demystify #NoEstimates, and explain why it is so controversial.

#Share an easy-to-use, bulk estimation technique "SwimLane Estimation", that I accidentally discovered while training an Agile team.

In addition, this video also answers the following questions

# How to Estimate User Stories
# What are Estimation Prerequisites
# What is the Definition of Done
# What are Reference Stories and how to easily create your own
# What are some Common Estimation Mistakes

There's a lot to come. So Stay Tuned.

00:00 - Intro
00:59 - Estimates vs NoEstimates
04:26 - When to use what
05:04 - How to estimate
06:24 - Definition of done
07:52 - Reference stories
10:12 - Swim Lane Bulk Estimation
12:14 - Common estimation mistakes
13:56 - Outro

**************************

Link to "Agile Product Planning", videos

1) How to define Product Vision

2) How to create a Product Roadmap (part-1)

**************************

Link to GRAVITAS video

***************

FREE DOWNLOADS:

Download my FREE Scrum Master Coaching Cards On how to resolve Conflicts as a Scrum Master here:

Download my FREE Scrum Master Coaching Cards On How To Create High Performing Teams here:

******************

LINKEDIN POSTS

Become part of the growing community with over 18500 professional Scrum Masters, Agile Coaches, Product Owners, and Project Managers by following me on LinkedIn, where I share Agile-related stories with practical tips, tricks, and workarounds.

****************

If you liked this video, please give it a THUMBS UP, SUBSCRIBE, and SHARE it with your friends and colleagues.

****************

WHO AM I?
I am an Executive, Agile, and Leadership Coach based in Toronto, Canada.

WHAT DO I DO?
I Coach Agile Coaches and help Executives / Organizations attain Business Agility.

WHAT I TALK AND WRITE ABOUT?
Thoughts on Agile Transformation; Agile Coach & Scrum Master Insights & tips;
Coaching & Leadership Skills; High-Performance Teams; Agile Frameworks particularly Scrum &
Kanban.

****************

[laup]

4:30 I like that, the most real world sattstement based on reality. Now a lot of companies are relying too much on estimation and then re-estimate even worse but you make a fair point, it's context dependent

[marvelousezechi]

I love the way you break things down, been watching a couple of your videos and it’s very comprehensive sir 👌 thank you 🙏🏽

[AndreiB]

Great video, thanks!
Small mistake at 7:12 :
The definition of done can actually be shared between multiple teams of the same product or even thoughout the whole organization, in some cases.

[daciamarkum]

Thank you! I have been trying to explain this to my new team and you are very thorough. I will be sharing this with them.

[prateekwatwale]

Hi Vibhor, thanks for the awesome explanation! I have been enjoying n leaning a lot from your videos. I have one request, If you could slow down pace of your speech a bit..it would give more time to listeners to absorb and understand the whole thing more easily as there is so much to pick from each video.

[elektrotigerRM]

Great. Thanks for showing a way to find references for different story points for other domains like systems engineering.

[ombudsmanGhana]

Thank you so much for a newbee learning from Coursera. You have a disciple because you teach well

[hcke]

Thank you Vibhor, great explanation! 🙏

[ifymbuk]

Many thanks for your videos. Always well detailed and easy to follow. Differnce between Acceptance Criteria and Definition of Done, well explained. Thumbs up!

[mugdhashah]

It was very detail video with practical tips. Thanks.

[kapilsachan]

Feedback- You gained one more subscriber 😊

[SrividyaNatarajan]

Hi Vibhor...I disagree on one point..the mistake 4...the ref. Baseline for a story will not change

It will change Vibhor. As the team gains experience, a 5 Storypointer could become a 3 Storypointer bcoz. There are now APIs which are reusable, and I have automated testing and my team also improved technically.

Let me know ur thoughts

[spuriusscapula]

Hey Vibhor, great videos. Could you please order your playlists? Thanks.

[romanzadorozhniy]

this comment's purpose is to support this channel and this magnificent video. Just kidding... or am I?)

[ramachandusharma]

Awesome explanation Vibhor. I have a question. Some teams calculating Dev estimate, Test estimate separately and summing those to get final story point instead of following relative estimate technique. E.g. if dev gives 3sp, tester gives 2Sp the overall estimate is given as 5sp where as actually this is a 3SP user story based on the reference story.

Also, is calculating individual velocity a right approach or an anti pattern? - Kindly throw some light on these questions.

[consultormid]

I have a question about the user story references technique.
Why you need first compute the total value (Complexity+Risk+Effort) for each user story selected then sorting, then, assign a Fibonacci value to finally have the final user story size?
What happend if assign the Fibonacci values from the beginning to my selected user stories, without the previous classification?
Did you explain this in another video?

Anyway thanks for this fantastic video about user story estimation

[DzmitryPutsiankou]

Hi Vibhor!
Thanks for you video!
Evaluation in SP or hours has its pros and cons, and in principle it is possible to justify the choice of any of them.

You said that converting SP to hours is a mistake, ok))
But what do you say to such a question: let's say you chose an estimate in SP; the team evaluated "effort"for this task = 5 SP.
we konow, that for billing purposes, all developers track the time in hours. After completing the task, we see 25 hours in this task.
How to assess whether the team got into the estimation or not for this particular task?
Bottle neck is that we have an estimate in SP, but the time tracking is in hours.

[MoundirRohmat]

Good content, keep it up ! But how do you think the team will be aligned and pick 5 US from 100 (for example)? for that you should review all the US?

[mirnalshishodia]

Hi Vibhor,

Can we decide reference stories on the basis of stories completed in the previous sprints? Actually, we decide our reference stories every quarter.

Thanks your videos are exceptionally well detailed.

I will be looking forward hearing from you.

[gottisher]

Hi Vibhor, your videos are really helpfull, thank you so much. I have a question though. Do you have a workflow of your own to work with the stakeholers, sme's and scrumteam such as lean inception?