Agile transformations are tough. That’s because wherever you start, the agile transformation creates culture clashes. Often, teams start with agile approaches. Teams discover the agile approach and practices that work for that team. Then, as the team gains experience, they refine their approach and practices. That’s the external part of what we see in an agile transformation. […]
Are you looking to help support your team, management, or organization’s agile adoption? Do you feel as if you are part of the formal or informal team leading your agile transformation? You need what Gil Broza and I teach and facilitate at the Influential Agile Leader Workshop. I wrote a number of posts about transformations:
How Do You Tell Your Agile Story? An agile transformation is a change, a big cultural change. Agile approaches change us as individuals, our teams, and our organizations. That means we can tell stories and help other people see what we learned. We’ve been telling each other stories—around the campfire, across the table, from the
Mark Kilby and I have finished the first four chapters of From Chaos to Successful Distributed Agile Teams: Collaborate to Deliver. We thought we had five finished chapters. Then we realized how much more work we had, to move from Google docs to Markdown. Sigh. We have four finished chapters 🙂 And, we know how to collaborate in
I delivered a webinar called Agile Metrics for Team and Product Progress last week, thanks to the nice folks at Innovation Roots. I had fun and so did many of the participants. One person gave me a new saying about metrics (at the end, during the Q&A): Are you data-driven or data-informed? It’s such a great
One of my clients has many reasons for wanting an agile transformation. Their old products are at the end of their lives. They need agile approaches so they can get feedback from customers as they develop the new products. They need to deliver to their customers more often. They need to create a mix of
I’ve been a part of geographically distributed teams since the mid-80s. I’ve taught and written about agile distributed teams for several years Now, I’m pair-writing a geographically distributed agile teams book with Mark Kilby. We’ve tweeted a little. We’ll be talking about our process at Agile 2018 in an experience report. We need your help.
Build Your Agile Tribe One of the reasons I use agile approaches is because they work. Not all of them, all the time. I find that I have to adapt my agile approach to the current context: the organization and its culture, the people, and the product(s) in development. Some people prefer to use a
Part of what makes an agile transformation difficult is the cultural change required. That’s what makes an agile transformation a journey. A client said to me, “I want the agile. The agile is good stuff: faster delivery of smaller stuff that we can get revenue for. I want it now. How fast can I get
I’ve been thinking more about possible measurements in an agile transformation journey. The first Possible Measurements post focuses on product throughput measurements. This post will focus on measurements you might see when the culture changes with an agile transformation. Again, do start with your why. Without knowing why you want to use agile approaches throughout the organization,