YDS: Do You Have the Courage to Speak Up in a Retrospective?

Do You Have the Courage to Speak Up in a Retrospective? Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley.

Professional Scrum Trainers Todd Miller and Ryan Ripley built this course to help those interested in Scrum get up and running quickly using the Framework. They've partnered with Daria Bagina from ScrumMastered to bring practical materials and guides to the course.

Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems.

For more information about Agile for Humans, visit:

For more information about Daria and ScrumMastered:

#ScrumMasterTraining #Scrum #ScrumFramework #ScrumMaster
#HowToBecomeAScrumMaster #ScrumMasterCertification #AgileForHumans #FreeScrumMasterCourse #FreeScrumTraining

[zenexmachina]

Suggestion? A video on your perspective of dependency management, particularly at scale, would be great. I'd love to hear your shared perspective.

[MisterAwesan]

The retro is IMO the hardest event for the scrum master. For example, it can easily turn into complaining about everything outside of the team's control. Or the team can just be quiet and not have much input. Or the team talks in circles, never getting to clear action points. Stepping in is necessary in each of those but it takes a lot of subtle skill to do well, and it's different in every team.

[CS-mqgd]

My take on retro is to be courageous to talk about impediments or opportunities of improvements as it pertains to product/sprint goal all while being respectful to the peer scrum team members. Making yourself available to help and asking for permission to help goes a long way in building trust and a cohesive working environment.

[tomaszniemiec]

Hmm, me as a Scrum Master? Of course! :D
What are they going to do? Fire me? XD I usually only ask questions or make suggestions when needed, while also moving the discussion to the point when the meeting is getting derailed.

From a team member's perspective, if a person has doubts about being vocal on a retrospective, this tells me that we have problems with the Scrum Values, but also with the team's psychological safety and without this there is not Agile. Also, a good tip: stop doing brainstorming and look into liberating structures :)

[psingh]

Got to share this channel to my scrum master coe. Well done.
Although I still believe Scrum is not the only way, just one of the many ways to be agile.

[mamarine]

One aspect of retros that I've struggled with in the past is the time box. It's important to respect the team's time and observe the time box. However, at times it is difficult to do that without seeming like you're trying to gloss over real issues the team is having. I've never been able to come up with a really good answer. For sprint retros, I try to keep it to 30min with small experiments we can run in the following sprint(s) to improve things. However, I've also run PI retros that take up to 1/2 a day and result in significant foundational shifts in how the team works - usually manifested in changes to the working agreement. There's a fine line between staying out of rabbit holes and making people feel valued.

[shanego]

Can you walk us through of a full working day of a scrum Master. What does he do all day?

[DrShraddhaPPawar]

Hey Ryan and Todd, Hope you are great. I have one question from my last interviewer.... suppose for single piece of work Team member A estimate 3 story points, member B estimate 9 story points and member C estimate 20 story points, given that there are no dependencies. Which one is right? And what should the SM do?

[patrickkelly]

Should managers be permitted to attend the retrospective ?