⚠ I'm giving FREE access to my EXCLUSIVE PRIVATE Agile Community to a lucky few. Visit this link to get access: agilecommunity.co/ If you liked this video, i'm sure that you will also like: kzfaq.info/get/bejne/aa-CjL2omdCtmoE.html (Management BELIEVES that the Scrum Team IS LAZY (do this as a Scrum Master..)) I want to hear from you. What topic do you want me to cover next?

Always grateful coach. The unique slants you always bring to mainstream agile issues are always thought provoking and beneficial. Thank you sir

Love it, great video and important too, adding onto the end of the 3 questions ‘towards the sprint goal’ is powerful and makes so much sense 🙏👍

I work in the video game industry as an associate producer and started a new project about 6 months ago (currently in prototyping phase). We have a team of 23 people right now (will grow later), 1 producer, 1 associate producer, 1 game director (kind of the product owner), 10 programmers, 4 game designers, 1 level designer, and 5 artists. My producer says we use scrum byt the tools and not by the book as it does not fit really well for the game insutry with projects that take 3-5 years, tight monthly deadlines/expectations from the publisher and a strickt budget. I try to get out of "working in isolation", but it is difficult. Our game designers alocate much of their time working with the programmers on their features, but they do need to design ahead. Also, with games having so many unique features, we have feature owners (sometimes designers, some times programmers) that specific people are only assigned user stories on thier specific features. So I find it very difficult and until now, impossible to break that cycle. I was on a project for 4 years before moving to this new one and there was a lot we did worng and I am trying to adjust for this new project. Any suggestions?

I really love this video.

I'm commenting here because @Scrumtuous told me to. And because it's great content.

Good q

I have a question about this video but first I want to thank you, your videos are very helpful. My question is more a concern about the roles you mentioned and the light waterfall that may be present in the sprints: If a Scrum Team have indeed a QA tester specialist that doesn´t program but only test, how can he start working from the beginning of the sprints if he needs to wait until the first story is ready for QA? this case is harder than you mentioned because the team actually is not isolated and also devs test things, also they work on different things but toghether so the first story that is ready for QA is not ready with all the others at the same time, but that doesn´t mean it doesn´t require some time (days) to be ready. So again, how can the QA start working from the beginning of the sprints if he needs to wait until the first story is ready for QA?

Another banger!

Need to plan every day? Sounds like something is broken