2025 Public Training Schedule
January 14 – 17, 2025 – Agile Analysis and Design Patterns – Half-Day Sessions
Follow me on Twitter:
Blog Post Categories
- Announcements {19}
- Articles {2}
- Bits and Pieces {74}
- Blogosphere {1}
- Bonuses {2}
- Build in Small Batches {27}
- Collaborate {38}
- Create CLEAN Code {34}
- Implement the Design Last {11}
- Integrate Continuously {30}
- Off-Topic but Interesting {3}
- Rants {82}
- Refactor Legacy Code {24}
- Say What, Why, and for Whom Before How {22}
- Seven Strategies {38}
- Specify Behaviors with Tests {17}
- Write the Test First {27}
Archives
Privacy Policy
(c) 2024 To Be Agile
- June 21, 2023
- Collaborate
When things go wrong, it’s natural to want to assign blame. But in agile software development, assigning blame doesn’t get us very far. And it can often make things worse. That’s why adopting a different mindset during retrospectives is crucial — one that focuses on the process, not the people.
Let’s face it – it’s usually not intentional when communication breaks down. People don’t set out to create problems or make mistakes. Instead, issues typically arise as a result of flaws in the process. By blaming individuals, we’re missing the root cause of the problem and making it more difficult to find a solution.
Instead of focusing on who made a mistake, we want to focus on what went wrong in the process that allowed the error to happen in the first place. This shift in perspective can significantly affect how we approach problem-solving.
When we focus on the process, we take the pressure off people. The team can focus on finding ways to prevent similar issues from happening again. By examining the process, we can identify the flaws that contributed to the problem and work together to improve it. This helps us avoid future problems and creates a more positive and collaborative environment.
To adopt this mindset, creating a safe and open environment where team members feel comfortable sharing their thoughts and ideas is crucial. This means avoiding blame and instead focusing on solutions. It also means encouraging everyone to share their perspectives and work together to find the best solutions.
Psychological safety is one of the essential factors in high-performing teams. Psychological safety doesn’t just mean that people feel safe sharing their ideas. It also means that the team is aligned with shared goals and practices. It means everyone on the team has a voice and feels heard, so they are encouraged to contribute.
We can create a more effective retrospective process by shifting our focus from blame to process. We can learn from our mistakes and make improvements that help us work better as a team. So, the next time something goes wrong, resist the urge to blame – instead, focus on the process and work together to find a better way forward.
Previous Post: « Look for Small Improvements
Next Post: Practice the Five Whys »