I hope this video was helpful. 📖 An in-depth practical guide for the Scrum Master job - Scrum Master Startup Guide: shop.scrummastered.com/product/scrum-master-starter-kit/ 📩 Subscribe to my newsletter to get updates on new stuff and special offers: scrummastered.com/free-downloads/

This self explanatory shows that you truly know your stuff.

very helpfull me coming from automation career and pivoting to IT stuff!

This is one of the best scrum videos I have watched so far. Very informative 🙏🙏🙏 Thank you so much

You rock Daria! Thank you for helping to understand what a productive and successful scrum master is. Tomaz

This video is on my top five all-time most helpful videos in addressing knowledge-vs-praxis gaps that never come up in training programs or certifications. I cannot thank you enough.

My problem is that I am someone who learns best by doing it myself. If I am being explained a concept or read about it, it’s hard for me to understand it deeply and remember it forever. The result us that I sometimes feel incompetent in my sm role

you are right. and seem like a great scrum master. but there's one thing you didn't mention. "using the software"... i've had only one really great scrum master in my career. he wasn't a coder. he had a degree in film history or something. but the thing that made him great was in genuine interest in the product we were building. he would have the latest version of what were building on his machine (he would even go through the build process himself). he would try and use the software to understand exactly what we just built and what work we have coming up. this really helped him understand how to help the team plan sprints and stories. he knew where the complex parts were. he know where the bugs were. he knew how the software was supposed to work. he may have not known how to code, but had genuine interest in what we were building. maybe this seems like an obvious thing scrum masters should do, idk. but i haven't had another scrum master like that since. ive had 3 or 4 different ones since then. all of them never had time to use/test the software we were building. they viewed themselves as "leaders", but knew nothing about what they were leading. there's always been a disconnect between the devs and the scrum master. my current scrum master complains that we get "too deep in the technical weeds" during out meetings. but we are just having normal conversations devs have during meetings.. it creates a tense environment where the devs need to be herded like children to keep them on track by the "adult" in the room... its extremely frustrating. thinking back on that one great scrum master i had, he involved himself in those conversations the best he could. he asked to be shown where the issue was. he asked general questions about the software. he wanted to understand the work he was helping to manage. and if conversations got far off the rails, we trusted him when he would guide us in another direction.

We moved away from scrum masters without a dev background due to bad experiences. It was like scrum painted by numbers rather than done with understanding, and they couldn't help the team adapt the technical problems to scrum or determine if the technical problems suited scrum. Scrum just isn't that complicated that it takes a full time position.

Thank you for your video. The background music is an additional cognitive load for those of us on the spectrum. I would recommend against it. A little bit of music goes a long way, and is workable for us when people are not speaking or if they are singing. But when people are talking, background sound effects are very challenging and cause us to click off.

Thank you for this video! really informative!! Best Scrum Chanel :)

Very good video! Very to the point!👏

Thank you very much. Super useful.

This is helpful.

Would you recommend a PSM-I certification over a CSM?

Truth be told, our Agile team currently have a scrum master who is really bad. A big problem is that she is not technical, and even when she presented herself as non-technical, it still became a problem with the team. The problem is that in the absence of technical understanding, the void becomes filled with political nonsense, contrived power and authority, driven in large part by fear of technical threats, leading to the scrum bum (aka master) to become overly adverserial.

I tried to schedule to see you so many times but for some reason it never worked out for me. So I was wandering what next?

Well summarised and this video should be used for businesses who fear change and who lack good practice.

Very informative ! Are you on Udemy?

Good stuff. another technical debt: not complying with the code coverage until closer to the release dates.