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 Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

#070 Die wichtigste Frage Deines Lebens