The most common agile retrospective focus is on the sprint (or iteration) that was just completed. For most agile teams, this is the past two weeks. We have many more options for retrospectives than simply looking back on the last sprint. We can look at a specific topic, an event, use a future focus, or look at a much longer timeline. Regardless of the focus, we are aiming to learn, generate ideas, and (ideally) agree on actions to take moving forward to improve to sustain.
Teams
Agile Safari – What’s Not Being Said?
Have you been in a situation where no one would bring up the problem that everyone knew was “in the room?” I’d guess that everyone has been there. So often, we don’t bring up the “elephant in the room.” For anyone who has not heard of this, the elephant in the room is a saying for the real or obvious truth that is not being addressed. Given an elephant in a room would be hard to miss, when people ignore it, they are typically pretending it is not there.
Building Antifragile Relationships and Teams @ Santa Barbara Agile
Building antifragile relationships is about finding ways for our relationships to gain from disorder, or be more antifragile. What tools and practices can we use to help us thrive from disorder? What mindset do we need to hold to be present with the teams and organizations we are in?
I’m excited to be presenting a session at Santa Barbara Agile titled: “Building Antifragile Relationships and Teams.” The session will be on November 19th! You can signup and find specific details at the Santa Barbara Agile Meetup.
Resolving Conflict by Working with Team Toxins
We know from Team Toxins and Team Conflict, that toxins are normal. So we can’t just “get rid of them.” In fact, pretending there are never toxins in a team could be viewed as a form of stonewalling. There are a number of ways to resolve conflict by working with team toxins. These not “iron-clad plans” or best practices, they are approaches to resolving conflict that ideally start before major conflict has emerged.
The four team toxins are criticism, contempt, defensiveness, and stonewalling.
Below I list a number of ways to work with team toxins. These are ideas that make or break our teams and relationships. I believe they make the difference between being engaged and checking-out. Many of these ideas are concepts that should be explored
Team Toxins and Team Conflict
Team toxins have the ability to wreak havoc on our teams and organizations if left unchecked.
Team toxins can lead to team conflict if people are not aware of and able to deal with toxins. Understanding team toxins is one preemptive way to deal with team conflict.
The four team toxins are:
- Criticism (or Blaming)
- Defensiveness
- Stonewalling
- Contempt
The Real Baseline Agile Retrospective Format
I always considered this six question format to be the Baseline Agile Retrospective Format. I say baseline instead of standard because a baseline is something to build on, not an ‘always the way’ standard (I know I’m splitting hairs here).
I believe the six question baseline agile retrospective format is a solid way to teach people how to do an agile retrospective. They can see, relatively clearly, the different parts that should be included. It can be a useful starting point to address additional questions and challenges.
Lessons-Learned vs Project Retrospectives
I wrote about agile team retrospectives in a recent article and find that the term retrospective can be used in many different ways. I’ve heard people ask, “Did you just change the name from lessons-learned to retrospective?” Although there are similarities, there are some key differences. Let’s review a few types and consider the issues with most lessons-learned meeting.
Release and Project Retrospectives
While agile team retrospectives have a team focus on celebrating, learning, and improving their relationship on a regular basis, there are other types of retrospectives.