Here's the recording of a talk I was lucky enough to give at the Lean Agile Exchange conference on "Three years of self-selection reteaming at Redgate".
This month I was interviewed by Sander Dur on his excellent Mastering Agility podcast to talk about Redgate's journey with self-selection reteaming over the last three years.
Crucial Conversations happen where the stakes are high, opinions vary and emotions run strong. These situations arise all the time in agile development teams and can lead to misunderstandings, inaction or strained relationships. In this post I'll explain when Crucial Conversations can pop up and give you some tips on how to tackle them.
The book Accelerate - The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations has been really important for Redgate over the past 12 months. It's helped us find a software delivery language that teams and the wider company understand and buy into, and allowed us to compare how we're performing against the best in the business.
When people talk about why they adopt an agile approach to software development, they talk about the many benefits of delivering working software iteratively. Rarely do I hear people call out the key reason why we should be taking an agile approach; it's part of the answer to giving people fulfilling and rewarding work.
At the end of June Redgate's Product Development organisation ran a retrospective session to review how things have gone in our corner of Redgate in the first half of 2019. This post explains how we ran the large scale retrospective and what we discovered by doing it.
What have the Wright Brothers, the original Boeing 737 and the Airbus A380 got to do with Redgate's internal development conference, Level Up 2019?
At Redgate we’ve found that development teams with clear purpose, self-direction and freedom to act were the most engaged and delivered amazing results. To shape all our teams to have these qualities we identified six key principles and unleashed our Fantastic Beasts!
The need to inspect and adapt is the fundamental concept at the centre of the agile software development movement. However, it often seems that the drive to inspect and adapt is only deliberately applied to what we build and not how we build. This means how a team works together, how they use the technologies at their disposal and how they apply processes can go unimproved.