This is one of the best presentations/webinars I've ever seen. And trust me... I've seen a lot materials. The speaker is definitely a SME on Agile and an excellent presenter.
Thank you for this presentation. I am preparing for a job interview and I especially like how you covered some of the pain points of working in agile with stakeholders that are used to fixed price/schedule/requirements agreements. Related to this I appreciate some of the philosophical language you used to explain the fallacy of “magic” and reasons for choosing value-based delivery. I’ve been through multiple trainings and watched a lot of videos and this is the best overview I’ve come across. Nice work!
Awesome presentation! Having worked on a lot of projects with quite varied Agile capabilities/optimizations, watching this video has been a nice revision (as in, homework/study) session, helping to put all that accrued knowledge and experience into perspective - a reminder of the truths and highlight of the fallacies.
Hi Sally, Webinar was very informative and clear many doubts. Thank you. Could you please also help with excel sheet link shown in the webinar. Link provided in video does not work. Thanks again
This is a wonderful and best presentations on Estimation mainly and i thoroughly loved every bit what she told in this video. I also like the excel sheet that she has maintained, would it be possible to share with us, if you could do so? That will be of great help. ~Bharath
A question, do you have a comparison between Scrum and RUP (Rational Unified Process), taking RUP as the "Traditional" instead of clasical Waterfall? The teams using RUP works with an iterative-inremental lifecycle very well shaped, and are also under a "predictive" premise. I wonder to know if there is a big difference vs Scrum. What do you think? RUP has been used since 1998 but its origin is older. Also by 2006 they make a RUP versión adapted to Agile
How the dynamic applied to The Team Plan at several levels (Release, Iteration and Daily) avoid negative connotation of micromanagement (in this case distribuited by Scrum Master, Product Owner and Scrum Team) ?
I have a big doubt, when run a Release planning meeting, should I evaluate all backlog asigning estimation for all user stories? after the first sprint the realease planning should be run again? what happen if the sponsor stablished and earlier due date for the entire project and in the release planning the estimation is more time required?
4 years old but still good, and your requirements one too. Although the sound on both have poor background noise. Recommend a microphone, if you haven't already got one now!
You had mentioned in your video, i could download the excel file you were referring in the video, but i cant seem to see a reference to it anymore. Could you kindly provide the information.. thanks
You are working on releases with a burn up chart for one team, that is straight forward enough when you know the sizing and their velocity (43 minutes in). When you have a large project with multiple teams and features shared across them you can't compare points across the teams therefore your release burn-ups don't work. This is the typical issue I see with this sort of planning. There is an additional problem with trying to size up a backlog where it is hugely unknown, you are back to not being able to give an answer of how big up front even if your velocity figures get better. Basically all of these techniques work when the projects are small, but what would you do with 20 Scrum teams working on a product being asked for an end date? It will fail.
Tim Field Curious how you confront this issue as I have run into similar problems on large, complex projects, especially those with cultural, contractual, or legal impediments to close collaboration or transparency.
I like agile, but I know that Strategic Planning and Portfolio Planning is not "Agile", that is from business side and is more related to the lifecycle to the business than "Agile", isn't it? The same, "Value" is defined and validated by the business not by "Agile". I believe some terms are used wrongly, are more alike to "sales paradigms" and false. We are not sellers, so we don't need to "married" with this wrong used terms. We are professionals who make the solutions and have the responsibility and ethic to use these terms rightly and avoid bad orientation to our IT people and business users/clients. Let's be ethic when we promote Agile, their paradigms are good enough and don't need to be falsified. What do you think?
Nonsensical comment of the day. Dumb even. And you did it in public! Wooohooo! Now everyone knows who you are.And this from a guy who liked a 10 minute video on how to rake leaves!!!
Quico Reed I agree, though in sentiment one of the things I struggle with is client stakeholders who hold the perception that planning is a waste of their money or expect the company to absorb planning costs as overhead. Since agile is much higher touch for the project/product manager as well as development teams, I see the value in it, but it is a point of contention in negotiations where there is an issue with the % of project time spent planning or managing vs “doing” specific deliverables. I like how she explains that this is just an illusion, but from that perspective (not the developers’), it does actually seem more involved and time consuming and therefore less “agile/efficient” for those in planning or staffing/resourcing roles.
This is one of the best presentations/webinars I've ever seen. And trust me... I've seen a lot materials. The speaker is definitely a SME on Agile and an excellent presenter.
This is the best agile estimation presentation, clear and thorough explanation on all the points.
Best video I've found on Agile Estimation thus far...
I agree.. really nice video with good examples.
Thank you for this presentation. I am preparing for a job interview and I especially like how you covered some of the pain points of working in agile with stakeholders that are used to fixed price/schedule/requirements agreements. Related to this I appreciate some of the philosophical language you used to explain the fallacy of “magic” and reasons for choosing value-based delivery. I’ve been through multiple trainings and watched a lot of videos and this is the best overview I’ve come across. Nice work!
this video is an eye opener for those who are new in Agile...... very informative and provides real world usage of the method.
One of the better presentations I have seen. Very practical.
One of the best presentation on Agile. What a knowledge base and confidence on this topic. Really helpful.
Detailed with practical applications. Great Job. I specifically liked the estimation approach based on complexity buckets for new agile teams
Gorgeous presentation!
Very nice explanation. Best video so far
Excellent Presentation, covers a whole lot of estimation issues, methods and approaches.
very good presentation and content, thanks Sally!
what a lovely presentation !Simply outstanding.
Awesome presentation! Having worked on a lot of projects with quite varied Agile capabilities/optimizations, watching this video has been a nice revision (as in, homework/study) session, helping to put all that accrued knowledge and experience into perspective - a reminder of the truths and highlight of the fallacies.
Hi Sally, Webinar was very informative and clear many doubts. Thank you. Could you please also help with excel sheet link shown in the webinar. Link provided in video does not work. Thanks again
This is a wonderful and best presentations on Estimation mainly and i thoroughly loved every bit what she told in this video.
I also like the excel sheet that she has maintained, would it be possible to share with us, if you could do so? That will be of great help.
~Bharath
Thanks for the presentation. Very useful. Is there a link to the presentation, excel spreadsheet for backlog etc.?
One of the best video seen on Agile estimations..
Can you please share or provide link to download the template shown at 2:28 in video?
A question, do you have a comparison between Scrum and RUP (Rational Unified Process), taking RUP as the "Traditional" instead of clasical Waterfall? The teams using RUP works with an iterative-inremental lifecycle very well shaped, and are also under a "predictive" premise. I wonder to know if there is a big difference vs Scrum. What do you think? RUP has been used since 1998 but its origin is older. Also by 2006 they make a RUP versión adapted to Agile
How the dynamic applied to The Team Plan at several levels (Release, Iteration and Daily) avoid negative connotation of micromanagement (in this case distribuited by Scrum Master, Product Owner and Scrum Team) ?
Very useful and informative video. Thank you Sally for sharing your knowledge with us.
Would be kind to share the sheet used in you example to manage the release plans and other stuff?
Thanks in advanced
awesome presentation, thanks for sharing.
I have a big doubt, when run a Release planning meeting, should I evaluate all backlog asigning estimation for all user stories? after the first sprint the realease planning should be run again? what happen if the sponsor stablished and earlier due date for the entire project and in the release planning the estimation is more time required?
This is what I was looking for a Long time now. Thanks for the presentation up there and all effort. 🙏🏼👍🏼
Great! one of the best presentation have seen on Agile ..thanks Sally for knowledge sharing
4 years old but still good, and your requirements one too. Although the sound on both have poor background noise. Recommend a microphone, if you haven't already got one now!
now 8 years old still good
Wonderful Session and great presentation.
Gr8 presentation Sally, could you please share its stuffs. Thanks
Thanks Sally... This is amazing educational video.
Amazing presentation..Just awesome
Great video - how does one get the zipped file with the templates?
Very good presentation. could you please share the excel sheet?
Hi, is there a way you can share that excel sheet?
Please where can l download sample agile software release plans?
You had mentioned in your video, i could download the excel file you were referring in the video, but i cant seem to see a reference to it anymore. Could you kindly provide the information.. thanks
excellent video! Publish more videos like this.
How will we come to know that user story of 8 points will be done in how many hours or days.?
Awesome video on Agile estimation.
I love your voice and clearly.
I got it. I attended the whole presentation , its marvelous. Thanks Sally
Can you please share the presentation and the excel template through some link?
A very good take. Shared on LinkedIn with your reference too.
Lovely presentation. Really information and to the point. Thank you.
Very informative will start the project. Thanks a lot
very well presented and easy to digest ... Thank you
Nicely put together. I loved the presentation.
Great work 👏
Superb session.Thanks much.
Can you please the template use at :2:48 on screen?
where can i get the download link for the excel sheet
Good explanation Agile estimation was very useful
You are working on releases with a burn up chart for one team, that is straight forward enough when you know the sizing and their velocity (43 minutes in). When you have a large project with multiple teams and features shared across them you can't compare points across the teams therefore your release burn-ups don't work. This is the typical issue I see with this sort of planning. There is an additional problem with trying to size up a backlog where it is hugely unknown, you are back to not being able to give an answer of how big up front even if your velocity figures get better. Basically all of these techniques work when the projects are small, but what would you do with 20 Scrum teams working on a product being asked for an end date? It will fail.
Tim Field Curious how you confront this issue as I have run into similar problems on large, complex projects, especially those with cultural, contractual, or legal impediments to close collaboration or transparency.
You would need to use a scaled agile framework, it's called SAFe. It's for your situation, precisely.
Thank you for sharing
Can anyone by chance share the presentation and the excel template? Many thanks ahead.
I've enjoyed the presentation. Nice work.
So impressed with this. Definitely learned lot!
. No doubt Best Video.on Agile Estimation . Can I claim 1 SEU against this video ?
great presentation.
Good video on estimation
Good one on estimation
Very helpful! great job!!
Great PPT...very nice
Great video, thank you very much!
very useful video, thanks.
this is a bit lengthy - but goes into great detail. well made!
Very Nice and informative
Awesome!! Thanks a lot for knowledge sharing
A very good webinar... 5*
really great video
It is amazing presentation!! Thanks much!!
You are a champion!!!! Thanks a Tonn!!!!!
Great presentation. Thanks!
Thanks Sally!
Thank you so much. You make my day :)
really nice Video
Good Presentations..Thanks!!
Very useful ... thanks !!!
Simply great !!!
Well explained
This presentation was very useful, thank you!
You are superb!
Great, Thanks
Best video
Great. Thanks!
i like this comparisation: 12:02
Good video
Thank you :)
awesome
Start @ 24 mins
I like agile, but I know that Strategic Planning and Portfolio Planning is not "Agile", that is from business side and is more related to the lifecycle to the business than "Agile", isn't it? The same, "Value" is defined and validated by the business not by "Agile". I believe some terms are used wrongly, are more alike to "sales paradigms" and false. We are not sellers, so we don't need to "married" with this wrong used terms. We are professionals who make the solutions and have the responsibility and ethic to use these terms rightly and avoid bad orientation to our IT people and business users/clients. Let's be ethic when we promote Agile, their paradigms are good enough and don't need to be falsified. What do you think?
LOUD.
CLICKBAIT!
58 minutes isn't very agile, no matter how excited you say you are.
Nonsensical comment of the day. Dumb even. And you did it in public! Wooohooo! Now everyone knows who you are.And this from a guy who liked a 10 minute video on how to rake leaves!!!
Quico Reed I agree, though in sentiment one of the things I struggle with is client stakeholders who hold the perception that planning is a waste of their money or expect the company to absorb planning costs as overhead. Since agile is much higher touch for the project/product manager as well as development teams, I see the value in it, but it is a point of contention in negotiations where there is an issue with the % of project time spent planning or managing vs “doing” specific deliverables. I like how she explains that this is just an illusion, but from that perspective (not the developers’), it does actually seem more involved and time consuming and therefore less “agile/efficient” for those in planning or staffing/resourcing roles.
Lovely presentation. Really information and to the point. Thank you.
Fantastic presentation....Thanks a ton..
Very good presentation, thx!
Great presentation. Thanks a lot!!!