Agile Coaches' Corner Dan Neumann at AgileThought

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!
 

This week, Dan Neumann and Justin Thatil are joined by Mike Guiler to continue their discussion of Norman Kerth’s book Project Retrospectives. In this episode, they dive deep into chapters 6, 7, and 8, analyzing some of the exercises and techniques described in the book and the immense value of learning to plan retrospectives for them to be fruitful. They close this conversation by addressing “postmortem” retrospectives and the importance of unpacking a failed project.
 
Key Takeaways
Chapter 6: Exercises and Techniques:
There are many ways to facilitate retrospectives and this chapter describes several intentional exercises meant to shake things up.
Norm addresses three essential parts of a retrospective: the readying, the past, and the future. The readying is meant to allow team members to prepare and bring forward relevant topics.
Teams often want to save time in retrospectives by skipping them or shortening their length. They do that because they find them ineffective and do not see the value in investing time and energy.
A Scrum Master must invest in making retrospectives into a much more impactful event for the team.
About facilitating better retrospectives:
Retrospectives need to take a longer time (three hours).
There needs to be “emotional freedom” in the group’s atmosphere to facilitate and enable members to participate; it’s crucial to be aware of different personalities and how they engage with others.
The topic’s sensitivity during the retrospective needs to be considered.
The postmortem retrospectives: When a project fails:
Be conscientious about not injecting your perspective; sometimes, it can do more harm.
An idea must be presented along with its benefits, strategy, and plan, including the costs and reasons why it is helpful to implement it.
 
Mentioned in this Episode:
Project Retrospectives: A Handbook for Team Reviews, by Norman L. Kerth
Agile Retrospectives: Making Good Teams Great, by Esther Derby and Diane Larsen
 
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!
 

This week, Dan Neumann and Justin Thatil are joined by Mike Guiler to share their continuous learning journey. They have been exploring the book Project Retrospectives written by Norman Kerth, and today, you will listen to them discussing chapters 3 to 5, where they dive deep into the role of Retrospective facilitators.  They compare Norm’s guidance against their own experience and reflect how practices presented are still be relevant today as retrospectives are more widely practiced in the industry.
 
Key Takeaways
Retrospectives: Internal or external facilitators?
You can be present without necessarily having to share your opinions and thoughts. 
An external facilitator for a Retrospective is not part of the Team but can be a well-informed outsider.
In the Scrum framework, very often it is the Scrum Master who facilitates the Retrospectives, but it does not have to be this way.
There is a conflict between a full contributor on the retrospectives and a facilitator, which is why an external facilitator can be significantly valuable.
Should Managers be in a Project Retrospective?
Managers must be allowed to be present at Retrospectives, but their involvement needs to be regulated.
Engineering retrospectives take time and effort.
Sometimes, the same feedback is received during several meetings, which is why it is important to plan retrospectives carefully considering Team Styles, the way the questions are brought forward, and any characteristics that can come up after thoughtfully observing the Team’s dynamics.
Identifying the most important topic for the Retrospective must be brought forward by the Team. The best achievement is when the Team expresses its needs as a result of the effective work of a facilitator (as opposed to someone dictating what the Team’s interest or need is).
 
Mentioned in this Episode:
Project Retrospectives: A Handbook for Team Reviews, by Norman L. Kerth
 
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!
 

This week, Justin Thatil, your host, welcomes Mike Guiler and Anitra Pavka. Today, they address the product discovery phase and some of the challenges the engineering Team usually faces while identifying what they will build and which special skills will be required to perform the task effectively. Also in this episode, they explore interviewing techniques and usability testing.
 
Key Takeaways
Interviewing users is universally helpful.
Interviewing users is so important that it should be done every week.
We need to be informed, and the only way to do this is by talking to the users.
Before the interview begins, you need to make sure you know what you want to obtain from the conversation. A discussion guide might help to lead an interview and make it more consistent.
Focus on allowing people to keep on talking.
Engage in the conversation with active listening skills 
Open-ended questions are ideal for promoting a deep conversation.
Fall in love with solving the problem and avoid fixating on a particular solution.
Put an effort into understanding the underlying motivations to solve a particular problem.
The organizational culture needs to promote the Discovery and Delivery Teams to talk to the customer and get feedback.
Encourage small experiments that try to address a problem from a different perspective and use a different tool to solve it. If the experiment is successful, the new approach could be applied to other matters.
Usability testing:
Was the product easy to learn? Was the user able to get through the product efficiently? Were there errors along the way?
Search to find out answers to questions about value.
You can use moderated and unmoderated usability tests to get the feedback the Team seeks.
Share the findings across the Team. They can influence how they approach the following prototype and evolve the solution.
 
Mentioned in this Episode:
 
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 on X (Formerly Twitter) @AgileThought using #AgileThoughtPodcast!
 

This week, Dan Neumann and Justin Thatil are joined by Mike Guiler to discuss the journey of a Project Manager shifting to fill the Scrum Master accountability. This episode mainly focuses on those Scrum Masters who are newer to this accountability and have a Project Management background. In this episode, they explore what happens when a Project Manager is assigned Scrum Master’s accountabilities which can develop differently depending on the person’s expertise and ability to learn and embrace Agile principles.
 
Listen to this episode to learn about the main aspects of a successful transformation.
 
Key Takeaways
It is common for the Project Manager (PM) to assume the role of the Scrum Master.
Scrum Masters who come from Product Management can incorporate their expertise in the process of shifting to Agility.
Product Managers often know a lot about the business domain.
PMs often have good relationships with the Team, which are crucial to initiating a transformation towards Agile.
You can’t easily hire for the business domain knowledge or the relationships.
It is often easier to have current staff learn a new way of delivering value.
A plan must be set in order to manage expectations between the development Team and stakeholders.
Many non-Agile do not know who the stakeholders are
Effective Scrum Masters will connect the team to the Stakeholders
The Scrum Master must ensure that the entire Scrum Team is engaged with its stakeholders, showing the development of software and articulating the plan. 
The Scrum Master does not need to take ownership of the relationship with its stakeholders but should empower the Team
How do we create more and better channels of communication with stakeholders?
Project Managers often see success as being on time and on budget.
As a Scrum Master, being on time and on budget is not enough; the most important thing is delivering the business outcome.
Status reporting is another area where PMs must work in transitioning to Scrum Masters.
When an Agile Team operates well, progress should be transparent.
Even status reports could become less valuable if the entire Team works together and is aligned, working with Sprint Reviews and information radiators.
 
Mentioned in this Episode:
Inspired: How to Create Tech Products Customers Love (Silicon Valley Product Group), by Marty Cagan
Project Retrospectives: A Handbook for Team Reviews, by Norman L. Kerth
 
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!
 

This week, Dan Neumann and Justin Thatil are joined by their colleague, Mike Guiler. In this episode, they explore how a Product Manager shifts from just management to leadership and how this transformation influences the role. Dan, Justin, and Mike discuss tools and strategies, including OKRs, Story Mapping, and Hackathons, among others.
 
Key Takeaways
Product management must study the market and users, becoming customer-centric and ensuring it is still viable for the business at the same time.
It takes more than one individual to effectively perform the discovery function. It's a Team effort (Product Designer, Product Owner, and a Technical member).
Discovery and design sessions are opportunities for Teams to unlock the art of the possible.
The Team has to learn from rapid feedback while ensuring steps are taken to not hurt organizational reputation.
A Product Manager must first understand how to help the Team approach a particular problem. A great way is to identify OKRs (Objectives and Key Results) and focus on the target market the Team is going after. Once the Team is aligned, the job can be done.
A Product Manager sets an objective for the Team and allows them to work autonomously toward reaching it.
Story Mapping: A Product Manager’s ally on the journey to product discovery.
Story Mapping is an easy way to frame what the Team is trying to achieve and the tool that might be the most efficient for that purpose.
Story Mapping can also help identify the target persona for which the Team is building a particular feature.
There is tremendous value in having the Team involved in Story Mapping and, as a result, immersed in and knowledgeable about the problem at hand.
Hackathons are a great way to keep a Team motivated.
Allow the engineers to explore; you will keep them engaged and motivated.
 
Mentioned in this Episode:
Fall in Love with the Problem, Not the Solution: A Handbook for Entrepreneurs, by Uri Levine
Inspired: How to Create Tech Products Customers Love (Silicon Valley Product Group), by Marty Cagan
 
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!