Artwork

Content provided by AgileThought and Dan Neumann at AgileThought. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by AgileThought and Dan Neumann at AgileThought or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

What Does “Good” Look Like in Agile? with Michael Guiler and Jim Beale

26:45
 
Share
 

Manage episode 376456967 series 3398142
Content provided by AgileThought and Dan Neumann at AgileThought. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by AgileThought and Dan Neumann at AgileThought or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

This week, your host is Justin Thatil, and he is joined by Michael Guiler and Jim Beale to answer one of the listeners’ questions: What does “good” look like for a Team during a sprint planning, a sprint, a PBI, or a backlog?

In this episode, Justin, Michael, and Jim share functional tips and great examples of what is considered good (and bad) in different crucial Agile moments.

Key Takeaways

  • What does “good” look like for sprint planning?

    • A good sprint planning starts with a good PBI.

    • It needs to state what the desired outcome is clearly.

    • Make sure there is plenty of collaboration on the PBI.

    • You need to have a healthy backlog.

    • Separate some time to look ahead; a fair estimation is needed.

  • What does a “bad” sprint planning look like?

    • Writing PBIs in sprint planning or the sprint; when you are behind the curve, you are winding them in real-time.

    • PBIs are written by the product owner. Or business analyst outside of the Team (working in isolation).

  • What does a “good” daily scrum look like?

    • It is great when the developer accountabilities start talking to each other.

    • A good sprint goal is essential (PBIs align with them).

    • Pay attention to where people are directing their comments.

    • Remember, this is a Team work where everyone is working collaterally.

Mentioned in this Episode:

Lead without Blame: Building Resilient Learning Teams, by Diana Larsen and Tricia Broderick

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 [email protected] or Tweet @AgileThought using #AgileThoughtPodcast!

  continue reading

331 episodes

Artwork
iconShare
 
Manage episode 376456967 series 3398142
Content provided by AgileThought and Dan Neumann at AgileThought. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by AgileThought and Dan Neumann at AgileThought or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

This week, your host is Justin Thatil, and he is joined by Michael Guiler and Jim Beale to answer one of the listeners’ questions: What does “good” look like for a Team during a sprint planning, a sprint, a PBI, or a backlog?

In this episode, Justin, Michael, and Jim share functional tips and great examples of what is considered good (and bad) in different crucial Agile moments.

Key Takeaways

  • What does “good” look like for sprint planning?

    • A good sprint planning starts with a good PBI.

    • It needs to state what the desired outcome is clearly.

    • Make sure there is plenty of collaboration on the PBI.

    • You need to have a healthy backlog.

    • Separate some time to look ahead; a fair estimation is needed.

  • What does a “bad” sprint planning look like?

    • Writing PBIs in sprint planning or the sprint; when you are behind the curve, you are winding them in real-time.

    • PBIs are written by the product owner. Or business analyst outside of the Team (working in isolation).

  • What does a “good” daily scrum look like?

    • It is great when the developer accountabilities start talking to each other.

    • A good sprint goal is essential (PBIs align with them).

    • Pay attention to where people are directing their comments.

    • Remember, this is a Team work where everyone is working collaterally.

Mentioned in this Episode:

Lead without Blame: Building Resilient Learning Teams, by Diana Larsen and Tricia Broderick

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 [email protected] or Tweet @AgileThought using #AgileThoughtPodcast!

  continue reading

331 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide

Copyright 2025 | Privacy Policy | Terms of Service | | Copyright
Listen to this show while you explore
Play