Agile Transformation Secrets, Part 2: Emphasize Collaboration If you’re trying to use agile approaches or manage an agile transformation, consider these three mindsets for you, your project, and your organization: Manage for change (Part 1) Emphasize collaboration. (this part) Use principles, not practices, so teams can be autonomous and deliver what they need to deliver. […]
Agile Transformation Secrets, Part 1: Manage for Change If you’re trying to use agile approaches or manage an agile transformation, consider these three mindsets for you, your project, and your organization: Manage for change (this installment). Emphasize collaboration. (I’ll send this in Part 2) Use principles, not practices, so teams can be autonomous and deliver
I spoke with an aspiring coach earlier this week. He asked me if people I ever coached were “resistant.” I don’t label people as “resistant.” If I need to label them, I think about this term, “People with data I should hear.” I like to think about what people resist, especially people in technical organizations.
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,
“What should I measure???” is one of the questions I see when I work with people going through an agile transformation. Too often, managers measure people as individuals. (Traditional measurements focus on resource efficiency instead of flow efficiency.) Resource efficiency measures don’t measure what the organization delivers or what prevents the organization from delivering. This
If you read my scaling agile series, you can see that becoming an agile organization requires seeing your organization as a system with a culture. You can start with teams, move to programs and the product part of the organization. If you don’t also address the cultural problems of rewards, you won’t continue with your
Agile culture is about the ability to change. (You need to know why you want to change, but once you know that, agile cultures promote change.) We (as agile teams and organizations) deliver something to get some feedback and learning. We use that feedback and learning about what we just did to challenge our assumptions
Ryan Ripley interviewed me on his podcast, Agile for Humans 83 about Create Your Successful Agile Project. We had a blast. I didn’t stint on my opinions or on my experience with agile teams. One of those opinions was about teambuilding, which I wrote about in Creating an Environment of Teamwork. The other opinion (based on