The larger your product, the more likely you have components teams. I often see component teams because of the architecture of the product. In this first image, the Integrated System Program, the rest of the product uses the Platform of Common Services as components. Also, the teams find it tempting to think of the common […]
Modern Management: Start with Congruence to Change Your Culture Do you want a more effective organizational culture that delivers more agility? Maybe you’ve tried agile framework for teams or products. While you’ve seen some improvement, you’re not where you thought you’d be. Instead of focusing on practices or team principles, consider changing your culture to
Many organizations ask teams to forecast when the team can deliver a feature. (Or finish a project.) That request often means the teams spend a ton of time forecasting, not delivering. Instead, what if managers told the team when the managers want to make a decision? The team could deliver enough to help the managers
I spoke with Andy Kaufman on his People and Projects Podcast 377. Full disclosure: I met Andy back in 1999 at the Software Development conference. So we’ve known each other for a long time. I subscribe to his podcast because I like the way he interviews guests. He looks beyond the obvious to deeper insights.
Please check out this wide-ranging conversation with Miljan Bajic. The writing workshop we mentioned now has its own page: Free Your Inner Writer & Sell Your Nonfiction Ideas. Enjoy!
I started this series with observations that my clients appear to confuse strategy and tactics. They think agile approaches are tactics and agile tools are part of their strategy. That’s why they want to Buy an agile approach. And that’s why they want to Customize and then standardize on tools. This post is about this
In Part 1 and 2 of this series, I wrote about how an agile approach might offer strategic benefits. And because an agile approach changes your culture, I said the agile approach was part of your strategy. So let’s ask this question: Can any tool—agile or otherwise—offer you a strategic advantage? (I don’t see how,
So when does it make sense to customize your agile approach to gain a strategic advantage? Whenever you have a unique problem to solve that’s strategic to your business. Let’s start with a couple of examples. Example 1: Startup/Small Organization with Few Products SmallCo has revenue of about $30Million a year. They offer their product
A number of my clients confuse their strategic ideas with tactical work. They think that the agile tools they use, such as boards, offer a strategic advantage. So they build or customize their tools. However, they adopt or “install” an agile framework or process without customization. Those actions lead to organizational brittleness. Instead, agile organizations
Some managers wanted to prevent Bad Things from happening in the organization, so they added policies or procedures. Now, these same managers want business agility. However, the policies and procedures increase friction and make it harder to get the Right Things done. It’s time to start removing some of those policies and procedures. The more