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
I’m struggling to write several posts and I realized I need to define my terms. I keep seeing managers confuse the strategic and tactical. That leads to large and unchangeable roadmaps and a lot of emphasis on predictability. I don’t know how to offer the level of predictability they want for large and unchanging work.
Three Ways to Rethink Your Business I received several thank you’s for the previous newsletter, Three Tips for Coping When You’re Supposed to Lead. I’m delighted that the issue resonated with so many of you. I’ve worked with several clients over the past weeks to help them rethink their projects, portfolios, and their business. Here are
I wrote a number of posts and newsletters over the past few weeks to help you see alternatives in this age of uncertainty. I hope you use these ideas to generate other ideas or ask more questions and create more experiments. The posts on this blog: 7 Tool Tips for Your Newly Distributed or Remote
Three Tips for Coping When You’re Supposed to Lead We’re several weeks into the COVID-19 crisis, and we still don’t know much about the future. We have some data about the present. But the future? Nope. You might have a title with “lead” or “manager.” And, you might not be sure about what to do
What Happened to the Beautiful Plans? (They Became Experiments) Tim, a senior manager, loved seeing plans for work and roadmaps. Then, the organization decided to Embrace, Not Manage Change. Tim wasn’t sure how to track the work. This image helps me frame the need for an agile approach. (See the blog series: Where I Think “Agile” is
Many people in the agile community promote a product orientation over a project orientation. That’s possible because an organization has product or feature teams. That works until you have more products than teams. That’s when you might still need projects to accomplish everything. If you keep teams together, you can still use projects in a
In an ideal agile world, the team would work directly with a customer. When you have a small product that serves maybe three types of customer (new, expert, admin for example), and that customer is down the figurative hall, you might not need any product people. You can create short feedback loops with your customer.
We have many words for people who shepherd the business value of a product. The many words aren’t a problem, as long as we can all agree on what these various people are and they take responsibility for. When we don’t agree, we run the risk of not managing our strategy, not thinking in terms