I sincerely thank you for this video. It really helps in keeping our faith and hopes in-place and re-establish our knowledge in this wierd and illogical world of fixed scope, traditional mindset, BAs working as POs, senior developers (tagged as leads) with rigid mindset of not doing anything else then coding and that too just in their tech domain, typical managers wanting to get the detailed out requirements in PBIs upfront rather than collaborating to refine it and even going further by just calling it done by coding for it disregarding the DOD and quality aspects. Sometimes it gets too frustrated to be a Scrum Master in such an environment clubbed with hard to coach management people like delivery managers who don't hesitate making more nonsense statements like doing separate coding and qa sprints or 1 Story Point is 8 hours without realising that team members take their such statements as the only right way to improve making SMs lives even harder...

Thanks for the shout-out :). Loved your analogies especially the musical instrument one.

Nice video! Refinement is an activity that serves multiple purposes. What I see a lot of teams struggle with is that they see refinement as a kind of early sprint planning. In my opinion, refinement is primarily about a collective understanding of the what and why. How the Developers are going to tackle the work in a technical perspective is part of sprint planning. Some Scrum teams see value in estimating during a refinement. (I find that a waste of time, by the way; I'd rather work with measuring cycle time and Monte Carlo simulations, but that's just a side note.) To estimate the scope of work, I see that a Developer still makes some kind of technical decomposition in the back of his mind. And that's okay. If the Developers' estimates of the scope of work differ, it is fine to share insights with each other in a technical sense as well. Estimating forces Developers to be concerned earlier than necessary with how they are going to do the work technically. Just enough, just in time remains difficult for many Developers. As a seasoned PST do you agree that making a (technical) plan is not part of refinement?

Great Video! Great Trainer!!!

What should the Scrum team do when they get unclear requirements? Accept or reject?

Hi Man! I've been leading projects for 3 years now but I really had difficulties understanding the differences between the roles and when is a specific role is relevant for a certain project or which SDLCs to implement. But thanks to your videos, I'm been enjoying learning a lot about scrum and project management. By far, your videos are the most interesting out there. Keep up the good work and please teach us more!

I'm a fan of you since you made a workshop in ralali djogjakarta, I were a participant

Thank you! You're doing an awesome job 😜

Hahahhahhahahhahaha omg i used to be a business analyst hahaha

Hi Coach, I got little confused, In the scenario when the member of the team try to refine the Product Backlog Item. You showed that the day of sprint is adding. So, Is it possible to put Backlog refinement inside the sprint? I'm sorry I got confused.