Daily Scrum Revolution! - If The Daily Sucks We Suffer Daily!

[@GaryStraughan]

"if the Daily sucks, we suffer daily." Nice!

[@AgileStateofMind]

Who doesn't love a good wordplay, right?

[@AmyBurns-bm1jm]

Another great video 💯and thought provoking. Our org is in a state of change and this gives me lots of ideas if I get shuffled around to a new project or team

[@AgileStateofMind]

Great to hear it can be of use, Amy😊

[@Paul_uk_3000]

Great content as always. Thought provoking for sure .

[@AgileStateofMind]

Thanks, Paul! Good to hear!

[@Rekettyelovag]

I learned (and experienced) people in (remote) teams tried to use a stand-up channel - weather it was for check ins and/or check outs - had lost the meaning of this event. Since there's no synchronous communication few and few people read what the others did/would do, everything gone to 1 task 1 person direction and all transformed into a report channel. The one most important purpose of the Daily Scrum is to create a plan( and a goal) for the next 24 hours. Conducting this async could be long, fiddly and dragged out. Especially if there're questions, problems lack of common direction outside of the Sprint Goal. If someone tries it and works, happy for them. But as a Scrum Master I think this is hard to turn around once it gets south. However I do understand that the time zone problem requires alternatives...

[@AgileStateofMind]

That's a valid call. Everything can go south. And there is no silver bullet. We need to accommodate for the company culture, team collaboration and so on. If we go to a team that barely understands the purpose of a daily scrum as is and ask them to start a channel instead, we will for sure fail with the approach. So yeah, that's why they need a Scrum Master to help them navigate the world full of options.

[@ashleys2144]

So much food for thought. Thanks again Maria. It's human condition to perpetually sought change - hence any regular event (i.e daily stand up / scrum ceremony) or in situ framework/work practice approaches arduousness when repeated ad infinitum, no matter what it is. The key is to identify dogma, discern any relevant fundamental value, and effect meaningful changes accordingly. Then just rinse and repeat - ad infinitum 🤓

[@AgileStateofMind]

😅😅😅

[@IslamicMediaWazNaat]

very nice video thank you Maria

[@madzero0]

Interesting topic. I agree with you that if something works for the team, they should do it. Something written in a guide shouldn’t stop them from doing that. If a team does the wrap up, how do you see the planning on taking the next step on reaching the Sprint Goal? Please correct me if I’m wrong but the feeling I get from this is during planning everyone gets their part of the work and they work on it until the end of the Sprint. The work is combined and tadaaaahhhhh, here is the Product Increment. And like I mentioned, if this works, please do so. But if it doesn’t don’t blame the framework. Just inspect and adapt.

[@AgileStateofMind]

My experience is that the teams that do the wrap ups are very proficient Slack users. Their Slack is full of updates, catch-ups, and stories. So they sync constantly on the work there. Also, usually they don't just stop doing online syncs they just have them less frequently.

[@TheShiftJournal]

Thanks Maria! There are no more important problems as a daily scrum.. ok maybe retros

[@AgileStateofMind]

Ha! Thanks Alona! Agreed, one could debate which is more important. However, as I say, if you hate your stand-up, you suffer daily! 😅

[@TheShiftJournal]

@@AgileStateofMind Agree 100%