And I was like, oh, I wonder who that is. I was at an agile conference down in Orlando and at lunchtime there was a round table with little sign that said Diana Larsen. We uh, call the little audible and what we were doing and so we are covering retrospectives today for me where some of the retrospective stuff started. Today’s topic is going to be retrospectives and with me again is my colleague Sam Falco.ĭan Neumann: Hey Sam, thanks for joining here. So I’d invite you to, if you have a topic you want as a future episode, send us an email at or tweet it to us with the #AgileThoughtPodcast and we will see about responding to that in the very near future. One of our goals here is to bring you agile topics in a really approachable way and we take a pretty broad view of what an agile topic might be. Now here’s your host, coach and agile expert, Dan Neumann.ĭan Neumann: Welcome to the Agile Coaches’ Corner Podcast and thank you for joining. The podcast for practitioners and leaders seeking advice to refine the way they work and pave the path to better outcomes. I ntro: Welcome to Agile Coaches’ Corner by AgileThought.
Master key ep 8 full#
Like what you heard? Check out our podcast page for more episodes full of interesting discussions, agile insights, and helpful resources.
Scorecasting: The Hidden Influences Behind How Sports Are Played and Games Are Won, by Tobias Moskowitz and L.Getting Value out of Agile Retrospectives - A Toolbox of Retrospectives Exercises, by Luis Gonçalves and Ben Linders.Agile Retrospectives: Making Good Teams Great, by Esther Derby and Diana Larsen.Agile Coaches’ Corner episode: “Setting Up Working Agreements with Christy Erbeck”.Agile Coaches’ Corner episode: “Exploring an Experimental Mindset with Adam Ulery”.Declaring your hands are tied and the problem cannot be fixed.Having a long list of too many things to change (which dilutes focus).Turning the retrospective into an unproductive complaint session.Covering the same issues every time without any experiment to fix it.Making the cycles too short and time-cutting due to no value.Ask or feedback as a facilitator to improve future retrospectives.Narrow down the list, make the list doable/actionable, hold people accountable, and follow through.Generate insights by digging deeper beyond the superficial issues by using the ‘5 Whys’.Track useful and pertinent data to bring to the retrospective.Engage the team in ‘setting the stage’ activities (as it is imperative for the team to effectively work together).The five phases of the Agile Retrospectives framework:.
Master key ep 8 professional#
Sam is an Agile Coach and Certified Scrum Professional with an extensive background leading agile development teams.ĭan and Sam dive deep into discussing Agile retrospectives, going over the five phases of the widely accepted framework from Esther Derby’s and Diana Larsen’s book, Agile Retrospectives: Making Good Teams Great. They also discuss what makes an effective retrospective, some of the failure patterns in unsuccessful retrospectives, and some great resources on retrospectives to follow up on after this week’s show! Joining Dan Neumann today is his colleague and return guest, Sam Falco. Today’s topic is all about retrospectives! A retrospective is a short meeting for project teams to reflect on the most recent stage of their project, analyze their processes, and identify issues or things they can do better, moving forward.
0 kommentar(er)
