How can the Scrum Master make the Daily Scrum more effective? with Hal Hogue

32:37
 
Share
 

Manage episode 328352198 series 2502498
By AgileThought and Dan Neumann at AgileThought. Discovered by Player FM and our community — copyright is owned by the publisher, not Player FM, and audio is streamed directly from their servers. Hit the Subscribe button to track updates in Player FM, or paste the feed URL into other podcast apps.

This week, Dan Neumann is joined by Hal Hogue to talk about the Daily Scrum event. Dan and Hal are assessing this topic again after two years, a particular couple of years since much has changed due to the strike of the COVID-19 pandemic, especially in regards to the workplace, making most of the work to be remote.

In today’s episode, Hal and Dan are talking about the ways in which the Daily Scrum can be more effective by fostering transparency and flow to promote simplicity and focus. They also dive deep into the struggles brought by remote working and the many alternatives to tackle this issue.

Key Takeaways

● What makes the Daily Scrum effective?

○ Understand the purpose of the Daily Scrum: What are we trying to accomplish with it?

○ The Daily Scrum is a perfect place for reflecting on how the plans are going; it is a reliable time and place to focus on refining the plan and thinking about what the next steps will be.

○ The Daily Scrum can be used to avoid misunderstandings.

● How to best avoid misunderstandings about information going back and forth among the Scrum Team members:

○ The Daily Scrum is an opportunity to inspect and adapt our plans and goals.

○ Establish transparency: Make sure things are visible, well understood, and agreed upon by all the Scrum Team members.

○ The purpose of the Daily Scrum is the opportunity for the Developers collaborate to achieve the Sprint Goal.

○ Be aware of “meeting fatigue”; people tend to have a lot of meetings and that can affect the predisposition to misunderstandings.

● Different ways in which a Scrum Master can foster transparency:

○ Give the Developers a chance to evaluate how confident they are about achieving the Sprint Goal by the end of the Sprint.

○ Developers can be encouraged to reflect on the current progress.

○ Transparency and flow need to go along with simplicity and focus.

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

226 episodes