Learn agile estimation in 10 minutes
HTML-код
- Опубликовано: 8 май 2014
- If you found this video useful, you might like to watch the entire course that was created as a result:
www.oreilly.com/library/view/...
Each of the videos follow this same style, plus there are exercises and more details about the underlying values of agile, and how they can be used to adapt agile to fit your particular needs. 
Наука
I am a certified Agile Coach, and this is probably the best Agile Estimation explanation I have ever seen. Thanks for sharing.
This was the best i have ever seen regarding estimation in Agile, even various online courses would not be able to tell this in their 5 hour recordings. Thanks
So True
It took my lecturer 4 three hour classes to explain this and I still left confused at the end. You did a fantastic job explaining everything in just 11 mins. Very well explained. Thank you 🙌🏻
The balancing between the story point and value point using "Bang for the buck" is important! Nice explanation
I took several online courses, and none of them could explain how to properly do an estimation. This is the best explanation on the web! Thanks so much for sharing!
This is the simplest and best explaination of the agile estimation in limited time. Thanks a lot.
Very crisp and clear. Thanks for the video David.
Beautifully done!!! It makes so much sense to me.
every time someone asks me, what the idea behind the story points is, I am sending him this video because it really left no open questions, thx for the good work!
Absolute gold. Perfectly and succinctly put.
Complex understanding is made very simple! Great to watch and understand the concepts. Thank you so much!
Standing ovation! this is the best explanation of story points I have come across in my career as an agile developer. Thank you so much!
Absolutely!
you're very kind what you invested in your video with , everything's clear you just helped me lots !
This is, in all palpable sincerity the best explanation for agile estimation I’ve seen❤
This is EXACTLY how I want everything in life to be taught.
So brilliant! Thanks
Great. i did not get the Agile estimation 100 % until i watched this. Thank you so much
Great video. In summary: In agile estimation, story points are used as an abstract time unit to avoid absolute time estimates, while value points measure task importance. The Fibonacci sequence is favored for story and value point estimation in agile because it fits human thinking.
simplest & best i have seen till now , keep it up. you rock
Outstanding -- had never heard of value points before.
Nice overview on Agile estimation. Loved the visuals and clear explanations. Thank you!
Very well explained. Clearly articulated the heart of the matter. Valuable !!
You are sooo good at explaining. Thank you so much for this video ♡
A clear-cut & very informative explanation. Maximum "Bang for the buck"!
superb, very well articulated!!! Thank you.
Thank you. This was a useful overview of Agile estimation
Great job! Clear and simple!
My friend, if there is a word more that excellent job, pls let me know!.
You have done an excellent job that the majority of Agile Instructors couldn't manage to do in 3 days of continuous talking.
Pls keep the good job up!
Your fan, from Iraq 🇮🇶
Excellent, clear, easy to understand. Many thanks.
Outstanding presentation - simple and clear!
Awesome, never seen better elucidation in this topic!
David requesting you to please continue making such very valuable to all, Thanks
Well you ask me four years ago, so I should probably start doing them again :D
WOW..... You explained it really good. Very easy, short and fantastic.
Great work!
Thank you!
Its such a great example for how story points works
Thanks so much, I struggled hard before this vid!
The following could help in some situations. Ann Latham suggested the following assessment:
1. Unfamiliar Complex
2. Unfamiliar Simple
3. Familiar Complex
4. Familiar Simple
LOL....it's Sept 2020, 6 years after this video. And I have to EXCELLENT. This is the best video., It is bang on with exactly what I've seen happen with my development team.
The best video yet! Just went through this sizing exercise yesterday at my job but had no idea how to apply. This is going to be so helpful for our next meeting. I understood the whole Fibonacci number adding, but how to apply it. That is where I needed help. Thank you!
Good explanation and very calm voice. Good job! 👍
Excellent explanation - most comprehensive video on this topic so far
Outstanding! Congratulations!
Great stuff!!, please upload more videos.
This was truly a great video. thank you.
very well explained! Thank u.
Well explained. Common topic with new information :) Thank you.
Thank you. That was very very helpful. Value points for this video 89, Story points, 13, BFTB = 6.8. This was on the top of my list. I shall mark the estimation task done now.
Awesome. This cant be explained any way better. Thank you..
I can't believe this video is 6 years old but still very relevant to how to estimate agile! Thanks a lot!
...I can't believe this comment is 3 years old but still very relevant! LOL!
@@payrollcontinuouslearningp3096 hahaha. Indeed!
Thanks a lot. Cleared every doubt in a most practical manner.
Thanks a lot for this valuable and neet video! Very helpful.
We don't have value point concept in our project as customers don't accord such point to a story. Product owner prioritised stories depending on how important it is for release deployment, in consultation with client. I enjoyed this video since explanation is incisive and invokes tremendous interest amongst Agile practitioner.
The best explanation, thanks!
awesome video! GOLD content! thank you!
Great video. Thanks a lot for sharing!
Beautifully explained
thanks so much for your clear explanation!!!
Thanks for taking a common topic and making it interesting video. Please add more videos
Short and sweet explaination.Thank you
Very nice explanation, Thanks so much!!
Very clear explanation. And very nice mindmap. I now understand the whole picture
Very well explained!
Great explanation, thank you 😇😇😇
precise. Thank you.
I love this video so much!
Useful. Thanks for the detailed information given.
Great!! Very well explained!
Kishore P. George h
very well explained ..Thanks
I want to thank you from the core of my heart for explaining such a tedious topic with so simplicity.
Thank You!
very well explained!
Excellent - thank you very much
thanks for making this digestible
perfectly Explained , Thanks
This is awesome!
Well Done !!
You are a good teacher , easy and makes sense ....not the bla bla bla .....insightful
Awesome story drawing👍
Very good method !
Perfect!!!
Very informative and I appreciate you sharing your experiences and knowledge. Could you please guide on the following:
1. Conducting a story point estimation throughout cross functional team means 1 representative from every functional group or all team members across organization?
2. A developer estimate 3 points for story vs tester estimate 8 points. Tester has to perform cross browser testing hence the scope of testing is large + different permutations/combinations to test the business rules. Which one will be taken as correct story point: 3 or 8?
3. Is there a baseline for effort based on story points e.g. 1 story point take 4 hours, 2 take 6 hours and so on
4. Say story point estimate consensus built on 3 story points. How do you schedule it if it's a 3 hour estimate by team. I mean in the end it will be development, testing, bug fixing, regression so will it be 3 hours each all the tasks together or 12 hours i.e 3 hours × 4 tasks
Thank you!
Brilliant!
In 11 minutes you did what my Master's Degree PM' professor didn't do in two years. Hope he is not here in this chat :) Thanks
Excellent
Thank you.
Best Explanation
Thank you for the valuable video explanation on estimations
Quite detailed
Excellent explanation 🙌👏👏👏🤩🙏
Good job 👏 👍
amazing! thx
This was great
Conflating story points with time is a fundamental misunderstanding of their use. They’re meant to convey complexity and risk. The reason we remove time from points is because different developers code at different rates of speed but, as a team, we need a way to relatively size the lift, agnostic to developer…
All Scrum masters should go through this.
Amazing
super !
Nice video, thanks. What is the point of all the ordering, prioritization processes & calculations until the BFTB sores & reordering, if the team would still have to brainstorm & reorder finally based on the dependencies? why not just prioritize based on the dependencies in the first place instead? like in the traditional PM
Awesome 👌🆒️
This was sooooo good. Where can I get more of his Vid? I only saw 2 on this channel 😔
Hello Rhea, It was actually turned into a full course by O'Reilly Media, which I drew and my wife narrated www.oreilly.com/library/view/the-agile-sketchpad/9781771376099/
How can the 'value-points' model apply to teams that have multiple, discrete stakeholders? How can the value-points of different stakeholders be evaluated against one another?
I was trying to apply this method, not to development, but on prioritizing some company projects. Then I found that the projects have an additional variable, which is material costs. That variable is not specifically considered in this model - let's say for development some of the stories require buying hardware or software which is not effort, but nevertheless affects the decision making process. Value and effort can be the sae for two stories, but one requires HW or SW costs which makes the other one a higher Bang for the buck.
Would you favor this cost be abstractly considered in the Story Points?
Or should we incorporate the actual cost of materials per story and incorporate via formula in Story Point or as a third number in calculation. Such as Value Points / (Story Points + Material Cost Points)?