Thanks! I like this method for getting initial points of reference for estimates. Every team I've been on that tried story points failed because they used time equivalencies as their initial reference point. This resulted in story points just being a measure of time rather than actually being relative estimates for effort/complexity.
Perfect Maria, this was really insightful. I would love if you could tackle some more technicalities, such as User Stories which are not complete in the Sprint and how do you deal with that Story Point wise, and another topic would be how to deal with lack of consensus on Story Points.
Hey! Oh that depends, if you do it before merging the story then yes but if you do it only after the whole new build is ready, then I'd say no. But better take it with the team! :)
I've officially replaced my senior Agile coach who I'm working with to learn this job better with your videos!!! Maria, you should write a book with all this great knowledge you share with us. Or create a course! Also, what video editor do you use? I'm ready to move beyond iMovie, finally, lol. Thanks sis!
Cindy you are such a darling! Thank you, I really appreciate that! I will think about it, because I love giving trainings :-) But you are killing it with iMovie! I love the transitions and using images/videos to illustrate what you are talking about! This is awesome and a lot of work! I start by iMovie (basic cutting) and then I move to Premiere Pro for more effects.
"Well, if I did invent story points, I’m probably a little sorry now, but not very sorry. I do think that they are frequently misused and that we can avoid many pitfalls by not using story estimates at all. If they’re not providing great value to your team or company, I’d advise dropping them on the grounds that they are waste. If, on the other hand, you just love them, well, carry on! ..."- Ron Jeffries, Story points creator. Just to clarify, story points were originally tied to days. The relative estimation approach that some teams use now is a variation that has become popular, but it may not align with the original intention. While it's fine to use them that way if it works for your team, it's important to be aware of their original purpose. Incorrect use of story points can lead to incorrect approaches in agile wow.
It would be kinda sad if all the approaches were only and exclusively applied as invented. I think it is good the tools and practices involve to adjust to the needs of an ever changing world ;-) Thanks for the quote!
My question not related to this tutorial .where are stored all completed projects,knowledge base,lesson learned, the templates ..they are stored in the company repository? this place in the organization is shared for BA ,PO ,PM and other stakeholder within the company the repository has a name but I have forget ..thank you
Hey, depends what you mean, it can be some wiki like Confluence, or other. Team can also document directly in the code, not sure if that is what you meant...
Or try COSMIC points, which are easier and probably more accurate ua-cam.com/video/HE6uq-geR7A/v-deo.html. I think they're as easy to use as story points, and maybe more accurate.
Wonderfully explained in a very easy language..Thank you for sharing
Thank you, Pawan!
Thanks! I like this method for getting initial points of reference for estimates. Every team I've been on that tried story points failed because they used time equivalencies as their initial reference point. This resulted in story points just being a measure of time rather than actually being relative estimates for effort/complexity.
happy to help! 😊
This is the best video on story point. Proud of you!
This was sooo simple and soo helpful!! Definitely subscribing to watch more of your videos
Aww, thank you, Kayla!
Great video. Reference stories may not exist with a brand new team with new company members. :) You then need to find some!
Perfect Maria, this was really insightful. I would love if you could tackle some more technicalities, such as User Stories which are not complete in the Sprint and how do you deal with that Story Point wise, and another topic would be how to deal with lack of consensus on Story Points.
Thanks for the comment, Filipe! I will see what I can do! :-)
Good one!
Thank you, Maria 🙌
Maria, if I have to calculate the story point for the testing effort of a user story, then shall I also include regression testing aspect?
Hey! Oh that depends, if you do it before merging the story then yes but if you do it only after the whole new build is ready, then I'd say no. But better take it with the team! :)
Good to know ☺️
I've officially replaced my senior Agile coach who I'm working with to learn this job better with your videos!!! Maria, you should write a book with all this great knowledge you share with us. Or create a course! Also, what video editor do you use? I'm ready to move beyond iMovie, finally, lol. Thanks sis!
Cindy you are such a darling! Thank you, I really appreciate that! I will think about it, because I love giving trainings :-)
But you are killing it with iMovie! I love the transitions and using images/videos to illustrate what you are talking about! This is awesome and a lot of work! I start by iMovie (basic cutting) and then I move to Premiere Pro for more effects.
do you still see value in story pointing/velocity/burndowns?
No I don't :) Yet, for those who have to suffer that, this is at least an easy guide on story points. Don't you think?
@@AgileStateofMind Agreed, everyone must start somewhere.
Great video!!!
Hmm...this was wacky. Subbed.
"Well, if I did invent story points, I’m probably a little sorry now, but not very sorry. I do think that they are frequently misused and that we can avoid many pitfalls by not using story estimates at all. If they’re not providing great value to your team or company, I’d advise dropping them on the grounds that they are waste. If, on the other hand, you just love them, well, carry on! ..."- Ron Jeffries, Story points creator. Just to clarify, story points were originally tied to days. The relative estimation approach that some teams use now is a variation that has become popular, but it may not align with the original intention. While it's fine to use them that way if it works for your team, it's important to be aware of their original purpose. Incorrect use of story points can lead to incorrect approaches in agile wow.
It would be kinda sad if all the approaches were only and exclusively applied as invented. I think it is good the tools and practices involve to adjust to the needs of an ever changing world ;-) Thanks for the quote!
My question not related to this tutorial .where are stored all completed projects,knowledge base,lesson learned, the templates ..they are stored in the company repository? this place in the organization is shared for BA ,PO ,PM and other stakeholder within the company the repository has a name but I have forget ..thank you
Hey, depends what you mean, it can be some wiki like Confluence, or other. Team can also document directly in the code, not sure if that is what you meant...
Everything in scrum is objective and complex. small team concept is good and not practical in incoperating with integration.
We could say that in Agile, it all "depends" 🙂
Brains and beauty.
Or try COSMIC points, which are easier and probably more accurate ua-cam.com/video/HE6uq-geR7A/v-deo.html. I think they're as easy to use as story points, and maybe more accurate.