In this week’s episode, Dan and Sam are diving into another fantastic listener question to address this topic! Chris on Twitter asked, “What is agile?” They take a deep dive into the history of why the Agile Manifesto was declared, the need that the principles and values were born out of, and ultimately: what is agile.

This week, Dan Neumann is joined by his co-host, Sam Falco, principal trainer and professional scrum trainer at AgileThought. Together, they’re exploring a question that was sent in by a listener. They asked Dan and Sam to share their take on “the Spotify Model.” The popularized model was first introduced in 2012 by the whitepaper, “Scaling Agile @ Spotify” and described a “people-driven, autonomous approach for scaling agile that emphasizes the importance of culture and network.”

Today, Dan Neumann is joined by Kristen Belcher, an Agile Coach who is saving the world, one retrospective at a time! In this conversation, Kristen shares her insights on how to effectively facilitate remotely. As someone incredibly knowledgeable on all things facilitation, Kristen shares how to make facilitation impactful and memorable, techniques for effective remote facilitation, what not to do when facilitating, and all of the other things you need to consider with remote facilitation!

This week on the podcast, Dan Neumann is exploring the journey of an agile transformation with Quincy Jordan, a Director in AgileThought’s Innovate Line of Service. Agile is no longer the new kid on the block. However, when a new organization decides that they want to benefit from adopting an agile practice, they are sometimes not aware that agility is a journey — not something where you install agile and walk away.

In the new Scrum guide update, one of the key but subtle changes has been on the phrasing that teams must be “self-organizing” to now saying that they must be “self-managing.” Joining Dan to discuss this topic and share his insights is return guest and AgileThought colleague, Michael Guiler. Mike is an agile consultant at AgileThought. He has been an agile coach for over 13 years and has experience helping geographically dispersed organizations to transform and better achieve their goals.

Today, Dan Neumann and Sam Falco are exploring the topic of teams — and not just Scrum teams, but all teams. As a leader, it can be difficult to manage many lines of communication — especially in larger teams. In Dan and Sam’s conversation, they discuss The Tuckman Model as a thinking framework on how to nurture high-performing teams. Tune in for today’s episode to find out which strategies you can put into play right now to build, lead, and maintain better teams!

This week, Dan Neumann is joined by two fellow AgileThought colleagues — Sam Falco, a Principal Trainer, and M.C. Moore, a Team Agile Coach. Together, they explore the topic of Scrum mastery — specifically, being a Scrum Master new into an organization. There’s a lot of excitement — but also many potential pitfalls — that come with entering a new group as a Scrum Master. And as someone who joined AgileThought just six months ago, M.C. Moore, in particular, has a lot of experience in this area!

Today Dan Neumann is joined by fellow AgileThought colleague and return guest, Andrea Floyd! Andrea is an enterprise agile transformation consultant at AgileThought with over 25 years of experience in software development and management. She is an innovator who has led multiple organization-wide scaled agile implementations, and she has also architected innovative solution strategies and roadmaps across many frameworks (including Scrum, Kanban, and the Scaled Agile Framework).

In this conversation, Dan and Sam highlight some of the ways in which companies and teams find what works for them, why perfect practicing agility isn’t the end-all-be-all, share the key characteristics for succeeding in agile, and, most importantly: why you shouldn’t be getting your agile shorts in a knot!

In this episode, part three of a three part series on the new Scrum Guide, Professional Scrum Trainer Sam Falco answers the question: "Why has self-organizing changed to self-managing in the new Scrum Guide”?