Every now and then Todd Miller and Ryan Ripley like to kick back, relax, and share an adult beverage with their Agile friends. This show is the result of those conversations. Tune in and learn about craft beer, cool t-shirts, weird nicknames, and some agile ideas along the way.

Every now and then Todd Miller and Ryan Ripley like to kick back, relax, and share an adult beverage with their Agile friends. This show is the result of those conversations. Tune in and learn about craft beer, cool t-shirts, weird nicknames, and some agile ideas along the way.

Craft Brewed Agile

Agile for Humans™ is a weekly podcast dedicated to the individuals and interactions that make agile work. The goal is to help create safe and collaborative working environments where people are empowered to do their best work.

Agile for Humans&trade; is a weekly podcast dedicated to the individuals and interactions that make agile work. The goal is to help create safe and collaborative working environments where people are empowered to do their best work.

A Podcast Devoted to Agile Product Delivery

Agile for Humans with Ryan Ripley and Todd Miller

CBA 005 - Getting into the Beer Flow

Todd and Ryan address a question about handling unplanned work that is not measured in Sprint planning and affects a team's predictability in meeting Sprint goals. They recommend holding back capacity back in Sprint planning to account for the unplanned work and plan realistically rather than at 100% capacity. They suggest cutting capacity in half if about half of the work in a Sprint is unplanned. They also caution against equating predictability with maintaining the same velocity or throughput and recommend measuring unplanned work transparently and gathering data on it.



⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc 

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

👉 Buy Fixing Your Scrum at Amazon: https://amzn.to/3BMvkcX 

✅Subscribe to our Channel to learn more about Agile, Scrum, and Kanban: https://www.youtube.com/agileforhumans?sub_confirmation=1 

For more information about Agile for Humans, visit:
Community: https://community.agileforhumans.com 
Facebook: https://www.facebook.com/agileforhumans
Twitter: https://twitter.com/agileforhumans 
LinkedIn: https://www.linkedin.com/company/agile-for-humans-llc

Todd and Ryan address a question about handling unplanned work that is not measured in Sprint planning and affects a team's predictability in meeting Sprint goals. They recommend holding back capacity back in Sprint planning to account for the unplanned work and plan realistically rather than at 100% capacity. They suggest cutting capacity in half if about half of the work in a Sprint is unplanned. They also caution against equating predictability with maintaining the same velocity or throughput and recommend measuring unplanned work transparently and gathering data on it.
 
⏩ Join Ryan and Todd for a Scrum.org course: <a href="https://buytickets.at/agileforhumansllc">https://buytickets.at/agileforhumansllc </a>
Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems.
👉 Buy Fixing Your Scrum at Amazon: <a href="https://amzn.to/3BMvkcX">https://amzn.to/3BMvkcX </a>
✅Subscribe to our Channel to learn more about Agile, Scrum, and Kanban: <a href="https://www.youtube.com/agileforhumans?sub_confirmation=1">https://www.youtube.com/agileforhumans?sub_confirmation=1 </a>
For more information about Agile for Humans, visit:
<ul>
<li>Community: <a href="https://community.agileforhumans.com">https://community.agileforhumans.com </a></li>
<li>Facebook: <a href="https://www.facebook.com/agileforhumans">https://www.facebook.com/agileforhumans</a></li>
<li>Twitter: <a href="https://twitter.com/agileforhumans">https://twitter.com/agileforhumans </a></li>
<li>LinkedIn: <a href="https://www.linkedin.com/company/agile-for-humans-llc">https://www.linkedin.com/company/agile-for-humans-llc</a></li>
</ul>

YDS: How Does a Scrum Team Handle Unplanned Work?

The video discusses who should facilitate a Sprint review in a Scrum team. Todd and Ryan believe the Product Owner should be involved in the process to ensure the right stakeholders are present to adapt the product backlog. However, the Product Owner doesn't necessarily have to be the one facilitating the Sprint Review but should be responsible for sending invites and ensuring the right people are in attendance. The Sprint review is seen as an underserved event that provides an opportunity to adapt the product backlog.



⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc 

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

👉 Buy Fixing Your Scrum at Amazon: https://amzn.to/3BMvkcX 

✅Subscribe to our Channel to learn more about Agile, Scrum, and Kanban: https://www.youtube.com/agileforhumans?sub_confirmation=1 

For more information about Agile for Humans, visit:
Community: https://community.agileforhumans.com 
Facebook: https://www.facebook.com/agileforhumans
Twitter: https://twitter.com/agileforhumans 
LinkedIn: https://www.linkedin.com/company/agile-for-humans-llc

The video discusses who should facilitate a Sprint review in a Scrum team. Todd and Ryan believe the Product Owner should be involved in the process to ensure the right stakeholders are present to adapt the product backlog. However, the Product Owner doesn't necessarily have to be the one facilitating the Sprint Review but should be responsible for sending invites and ensuring the right people are in attendance. The Sprint review is seen as an underserved event that provides an opportunity to adapt the product backlog.
 
⏩ Join Ryan and Todd for a Scrum.org course: <a href="https://buytickets.at/agileforhumansllc">https://buytickets.at/agileforhumansllc </a>
Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems.
👉 Buy Fixing Your Scrum at Amazon: <a href="https://amzn.to/3BMvkcX">https://amzn.to/3BMvkcX </a>
✅Subscribe to our Channel to learn more about Agile, Scrum, and Kanban: <a href="https://www.youtube.com/agileforhumans?sub_confirmation=1">https://www.youtube.com/agileforhumans?sub_confirmation=1 </a>
For more information about Agile for Humans, visit:
<ul>
<li>Community: <a href="https://community.agileforhumans.com">https://community.agileforhumans.com </a></li>
<li>Facebook: <a href="https://www.facebook.com/agileforhumans">https://www.facebook.com/agileforhumans</a></li>
<li>Twitter: <a href="https://twitter.com/agileforhumans">https://twitter.com/agileforhumans </a></li>
<li>LinkedIn: <a href="https://www.linkedin.com/company/agile-for-humans-llc">https://www.linkedin.com/company/agile-for-humans-llc</a></li>
</ul>

YDS: Who Facilitates the Sprint Review in Scrum?

The video discusses methods for identifying waste and workflow bottlenecks, particularly in lean principles. Ryan and Todd suggest using flow metrics to identify trends, running activities with teams to identify specific issues, and validating that input through visualizations. Balancing efficiency with effectiveness and keeping the customer in mind is also emphasized.

⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc 

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

👉 Buy Fixing Your Scrum at Amazon: https://amzn.to/3BMvkcX 

✅Subscribe to our Channel to learn more about Agile, Scrum, and Kanban: https://www.youtube.com/agileforhumans?sub_confirmation=1 

For more information about Agile for Humans, visit:
Community: https://community.agileforhumans.com 
Facebook: https://www.facebook.com/agileforhumans
Twitter: https://twitter.com/agileforhumans 
LinkedIn: https://www.linkedin.com/company/agile-for-humans-llc

The video discusses methods for identifying waste and workflow bottlenecks, particularly in lean principles. Ryan and Todd suggest using flow metrics to identify trends, running activities with teams to identify specific issues, and validating that input through visualizations. Balancing efficiency with effectiveness and keeping the customer in mind is also emphasized.
⏩ Join Ryan and Todd for a Scrum.org course: <a href="https://buytickets.at/agileforhumansllc">https://buytickets.at/agileforhumansllc </a>
Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems.
👉 Buy Fixing Your Scrum at Amazon: <a href="https://amzn.to/3BMvkcX">https://amzn.to/3BMvkcX </a>
✅Subscribe to our Channel to learn more about Agile, Scrum, and Kanban: <a href="https://www.youtube.com/agileforhumans?sub_confirmation=1">https://www.youtube.com/agileforhumans?sub_confirmation=1 </a>
For more information about Agile for Humans, visit:
<ul>
<li>Community: <a href="https://community.agileforhumans.com">https://community.agileforhumans.com </a></li>
<li>Facebook: <a href="https://www.facebook.com/agileforhumans">https://www.facebook.com/agileforhumans</a></li>
<li>Twitter: <a href="https://twitter.com/agileforhumans">https://twitter.com/agileforhumans </a></li>
<li>LinkedIn: <a href="https://www.linkedin.com/company/agile-for-humans-llc">https://www.linkedin.com/company/agile-for-humans-llc</a></li>
</ul>

CBA 005 - Getting into the Beer Flow

In 2 playlist(s)

Agile for Humans with Ryan Ripley and Todd Miller

Social links

Follow podcast

Recent clips