33 subscribers
Pergi ke luar talian dengan aplikasi Player FM !
Podcast Berbaloi untuk Didengar
DITAJA


1 Pushing Past Stagnation & Business Plateaus 30:21
Project Retrospectives: Book Exploration (Part 3) with Dan Neumann, Justin Thatil, and Mike Guiler
Manage episode 421299185 series 2502498
This week, Dan Neumann and Justin Thatil are joined by Mike Guiler to continue the discussion on Norman Kerth’s book Project Retrospectives. In this episode, they explore the last three chapters, which are filled with exercises to apply at Retrospectives, specifically when sensitive topics are to be addressed.
Key Takeaways
Some Retrospective activities are designed to address emotionally charged topics.
Failure must be accepted and embraced in postmortem retrospectives; otherwise, no one would be open to discussing it.
As a facilitator, try to find the highest leader available in your organization that is willing to share with participants an instance in which they themselves faced failure and what he or she learned from it. This establishes that it is okay to talk about failure.
Becoming a Facilitator:
You have to “walk the walk”; facilitators are made by practice.
Ask for help when you need it! Don’t be afraid to ask for assistance when your capabilities are limited.
As a facilitator, you can also contact someone outside your organization for support.
A useful resource is getting feedback from a second facilitator about the Retrospective. Don’t be defensive; feedback is always an opportunity to grow.
Allow space for intense emotions during Retrospectives. Fostering the expression of emotions is healthy and cathartic for the organization, but sometimes, it can be challenging for the facilitator to deal with them during the event. Listen actively, assign a meaning to those feelings, and try to identify the feeling arousing about that feeling. Identify which feelings can be discussed at the Retrospective and which others should be addressed one-on-one.
Tools for Facilitators:
Ask for help.
When something isn’t working, try something different. Be humble enough to know when to pivot.
Avoid triangulation. Encourage people to talk to the person, not about the person.
Congruent vs. incongruent messaging: When delivering a message that describes a problem, first address how the problem is impacting you (the self), then the context, and finally, the intention and how this caused the problem. A similar approach is the Situation-Behavior-Impact framework.
What to do after Retrospectives?
Collect the readout: Make a summary of what was done in the Retrospective.
Collecting a library of Retrospectives can help estimate projects. Retrospectives contain a significant amount of useful data for the organization.
After recapitulating the event, think about what can be improved.
The information coming from Retrospectives is a great way for a better forecast.
Mentioned in this Episode:
Project Retrospectives: A Handbook for Team Reviews, by Norman L. Kerth
Intuitive Prediction: Bias and Corrective Procedures, Daniel Kahneman
Listen to Project Retrospectives: Book Exploration (Part 1) and (Part 2)
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!
332 episod
Manage episode 421299185 series 2502498
This week, Dan Neumann and Justin Thatil are joined by Mike Guiler to continue the discussion on Norman Kerth’s book Project Retrospectives. In this episode, they explore the last three chapters, which are filled with exercises to apply at Retrospectives, specifically when sensitive topics are to be addressed.
Key Takeaways
Some Retrospective activities are designed to address emotionally charged topics.
Failure must be accepted and embraced in postmortem retrospectives; otherwise, no one would be open to discussing it.
As a facilitator, try to find the highest leader available in your organization that is willing to share with participants an instance in which they themselves faced failure and what he or she learned from it. This establishes that it is okay to talk about failure.
Becoming a Facilitator:
You have to “walk the walk”; facilitators are made by practice.
Ask for help when you need it! Don’t be afraid to ask for assistance when your capabilities are limited.
As a facilitator, you can also contact someone outside your organization for support.
A useful resource is getting feedback from a second facilitator about the Retrospective. Don’t be defensive; feedback is always an opportunity to grow.
Allow space for intense emotions during Retrospectives. Fostering the expression of emotions is healthy and cathartic for the organization, but sometimes, it can be challenging for the facilitator to deal with them during the event. Listen actively, assign a meaning to those feelings, and try to identify the feeling arousing about that feeling. Identify which feelings can be discussed at the Retrospective and which others should be addressed one-on-one.
Tools for Facilitators:
Ask for help.
When something isn’t working, try something different. Be humble enough to know when to pivot.
Avoid triangulation. Encourage people to talk to the person, not about the person.
Congruent vs. incongruent messaging: When delivering a message that describes a problem, first address how the problem is impacting you (the self), then the context, and finally, the intention and how this caused the problem. A similar approach is the Situation-Behavior-Impact framework.
What to do after Retrospectives?
Collect the readout: Make a summary of what was done in the Retrospective.
Collecting a library of Retrospectives can help estimate projects. Retrospectives contain a significant amount of useful data for the organization.
After recapitulating the event, think about what can be improved.
The information coming from Retrospectives is a great way for a better forecast.
Mentioned in this Episode:
Project Retrospectives: A Handbook for Team Reviews, by Norman L. Kerth
Intuitive Prediction: Bias and Corrective Procedures, Daniel Kahneman
Listen to Project Retrospectives: Book Exploration (Part 1) and (Part 2)
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!
332 episod
Semua episod
×
1 AI: A New Thinking Partner in Agile Teams with Dan Neumann 16:03

1 Maximizing Team Autonomy while Maintaining Accountability in Agile Frameworks with Dan Neumann 18:37

1 Tips for Managers to Help Agile Teams with Dan Neumann 15:16

1 Project Inception Activities: Setting the Stage for Success with Mike Guiler 33:52

1 Excellence Exhaustion: What Is It and How to Prevent It, with Nina Sossamon-Poghe 40:00

1 Kanban Essentials: How and When to Start with Mike Guiler 23:44

1 A Journey into Project Retrospectives with Norm Kerth 37:13

1 Liberating Structures with Kristen Belcher 39:36

1 Seven Tips for Agile Facilitation with Dan Neumann and Justin Thatil 37:41

1 Main Challenges of Product Practice with Ned Pope 37:31

1 Complementary Practices in Scrum with Mike Guiler 30:50

1 The Importance of Performance Engineering in an Agile Team with Jeannine Gonyon 28:45

1 Developing Better Results with Gil Broza 35:18

1 Project Retrospectives: Book Exploration (Part 3) with Dan Neumann, Justin Thatil, and Mike Guiler 32:46

1 Project Retrospectives: Book Exploration (Part 2) with Dan Neumann, Justin Thatil, and Mike Guiler 26:39

1 Project Retrospectives: Book Exploration with Dan Neumann, Justin Thatil, and Mike Guiler 21:21

1 Product Discovery and Delivery: The Importance of Using Interviewing Techniques and Usability Testing with Mike Guiler and Anitra Pavka 33:06

1 Shifting to Agility: From Project Manager to Scrum Master with Mike Guiler 32:25

1 From Product Manager to Product Leader with Mike Guiler 33:55

1 How Managers Support Teams Shifting to Agile with Mike Guiler 30:04

1 How Agile Organizations Support Their Managers with Mike Guiler 33:47

1 Developing a Successful Mindset with Seth Maust 30:44

1 Encouraging accountability as a key driver for results with Mike Guiler, Jim Beale, and Mariano Oliveti 38:30

1 DevOps: Creating Safety and Value with Mariano Oliveti and Erica Menendez 31:04

1 Being Human-Centric in Software Development with Anitra Pavka 34:15

1 Growing as a Coach: An Agile Journey with Mariano Oliveti 29:28

1 Kanban Method: Improving Your Process Framework with Joey Spooner and Todd Little 38:47

1 Flawless Execution with James D. Murphy 34:21

1 Delivering High-quality Agile Projects with Erica Menendez and Mariano Oliveti 27:48

1 MVPs and MMPs: Solving Problems the Most Effective Way with Erik Lindgren 30:04

1 How can I scale Scrum? The Nexus Framework (Part 2) with Rich Hundhausen 32:23

1 How can I scale Scrum? The Nexus Framework (Part 1) with Rich Hundhausen 25:20

1 Scope Creep: The Art of Prioritizing with Erik Lindgren 32:40

1 Is this Agile? with Dan Neumann and Justin Thatil 34:46

1 Why Do Some Organizations Dislike Agile? with Michael Guiler and Mariano Oliveti 35:06

1 Cultural Impact on Agile Transformation with Rich Visotcky 39:06

1 Agile Hybrid Working with Dan Neumann 25:32

1 Professional Sports and Agile: Shared Frameworks and Principles with Quincy Jordan and Pamela Dukes 40:36

1 The Future of Agile with Misi Eyetsemitan 30:39

1 From Agile Coach to Manager with Hal Hogue 38:21

1 Seamless Value Flow with Lizmeth Rodriguez and Justin Thatil 36:18

1 Mastering Agile: Balancing Dreams, Budgets, and Discipline 32:42

1 Empowering Teams: Fostering Autonomy and Accountability with Mariano Oliveti and Erica Menendez 32:25

1 Balancing Technical Prowess with Product Ownership with Erica Menendez and Phillip Lisenba 29:33

1 Are Agile Assessments your Friend or Foe? with Justin Thatil and Mike Dionne 30:58
Selamat datang ke Player FM
Player FM mengimbas laman-laman web bagi podcast berkualiti tinggi untuk anda nikmati sekarang. Ia merupakan aplikasi podcast terbaik dan berfungsi untuk Android, iPhone, dan web. Daftar untuk melaraskan langganan merentasi peranti.