Agile Transformation Secrets, Part 3: Principles Over Practices 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. (Part 2) Use principles, not practices, so teams can be autonomous and deliver what they need to […]
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.
Three Secrets for Improvement by Subtraction Too often, when we change something, we add to our established practices. However, many changes succeed only when you subtract something. What will you stop? Here are three questions you might consider: Who needs information in what form? Who needs to work together? Who needs the work? Secret 1:
I’ve been pair-writing a book with Mark Kilby, From Chaos to Successful Distributed Agile Teams: Collaborate to Deliver. We hit a big milestone today: We published the first complete draft today. We’ve been working on this book for a year. It’s much better because of our collaboration. We reflected a little on our success to
When I teach any sort of product/project/portfolio management, I ask, “Who believes multitasking works?” Always, at least several managers raise their hands. They believe multitasking works because they multitask all the time. Why? Because the managers have short work-time and long decision-wait time. If you are a manager, your time for any given decision looks
See Your Agile Collaboration Traps In honor of the impending Create Your Successful Agile Project book release, I decided to send you a four-part series about agile traps. Yes, one for each piece of the subtitle. This one is the collaboration trap. Here are three common collaboration traps: Your team is a component team. (The
I have a new book in beta, Create Your Successful Agile Project: Collaborate, Measure, Estimate, Deliver. (The in beta part means that it is in copyediting, and then onto layout and print. It’s a process.) I’m so excited about this book. My three most recent Pragmatic Manager newsletters were about jelled teams: The Case For
We might start to think about agile approaches as a project change. However, if you want to “scale” agile, the entire culture changes. Here is a list of the series and how everything changes the organization’s culture: Defining “Scaling” Agile, Part 1: Creating Cross-Functional Feature Teams. Without feature teams, I don’t see how you can
One of the challenges I see in organizations is how managers can use agile approaches. One of the biggest problems is that the entire organization is organized for resource efficiency (think silos of functional experts). Agile approaches use flow efficiency. Thinking in flow efficiency changes everything. Many people in organizations believe that dividing up the
Note to my dear readers: As I write, I realize this series is growing. Thank you for your understanding in advance. In Defining “Scaling” Agile, Part 4: Sharing Agile Outside of Product Development, I wrote about an independent workgroup with one stream of work. I used Customer Support as an example. Support has one stream: