People have asked me “How can I get my execs to support an agile transformation? They don’t like that they can’t predict anything.”
Reframe the Agile conversation around value
This is never going to be an easy conversation, but I recommend reframing it from the outset. Don’t talk about scrum or methodologies or the Agile Manifesto. Instead, talk about delivering value to the market and how your products and your company can be more successful.
Among the things keeping executives up at night are the following three questions:
- How can I get higher quality products to market faster?
- How can I motivate my teams and help them improve?
- How can I stop failing in my predictions of what we’re going to deliver?
Help your executives sleep better
If you take these questions to heart, you’ll find there are solutions. And as you implement these solutions, you end up doing agile or something that looks very much like it. (Another way to say this is that you implement agile to get good answers to those questions.)
- To get higher quality products to market faster, you need to focus on and prioritize adding the highest value capabilities to the products. And you must stop adding low value capabilities. You get two benefits from this. First, because you aren’t working on lower value stuff, the time the team spends is intrinsically higher value. And second, your team is naturally going to be more motivated because they are working on higher value stuff. Focusing on value helps with the first question and part of the second question.
- I’ve already talked about how to motivate your team more effectively. How do you help them get better? How do you accelerate your team’s learning cycle? You make the cycle of review and learning a lot faster. The “retrospective” is a key part of the scrum methodology for just this reason. The team does its learning as closely as possible to the action. It also helps if you can have the team accomplish things on that short cycle as well. You may need to do clever partitioning of those important things you are working on.
- There’s only one way to stop failing in your predictions. You must stop trying to predict the future. We all know it doesn’t work. Even if you have a concrete plan, with “good” estimates, you will not hit it. (It’s never been done.) Instead of predicting what you will deliver when, use a value-based approach to talk about what’s coming. You can confidently say “Every release will have the most valuable capabilities we could deliver in the time frame.” You may not know exactly which capabilities those will be in advance. But you can be confident they are the most valuable things you could possibly deliver. So rather than focusing on hitting a schedule – which is an internal target that customers mostly don’t care about at all – you are focusing on delivering value to customers – which customers do care about, which is much more valuable.
I’ve separated maximizing the value of the results the team delivers from continuously improving the team’s ability to deliver.
These two ideas are often munged together in agile discussions. Indeed, by focusing your team on delivering value fast, the team naturally gets more motivated and faster.
But the second half, of accelerating the learning of the team, is not necessarily about “agile.”
The practice of retrospectives or debriefs gives you the other dimension of team improvement – continuous learning. To accelerate continuous learning, you need to make the pace of the retrospectives faster. It’s much better to do learning near the actual experience. And since agile methodologies have short sprints, doing a retrospective for each sprint is a natural way to accelerate learning.
From Value-focused to Agile
If you combine all these thoughts, there are four aspects that combine to make more productive teams:
- Making sure you’re always working on the most important thing or things
- Continuous learning
- Not predicting the future
- Fast paced iterations
And, if you have those four things, you get four side effects, all very valuable:
- Agile as a side effect
- More effective teams as a side effect
- More revenue faster as a side effect
- Higher value products to market faster as a side effect
And there’s one other side effect. If you are working in order of importance, you can also push that practice back to the requirements and planning stages. The product managers only need to write requirements and do planning on the next most important capabilities. Requirements for less important capabilities can be delayed until they are needed. This means the development process can start sooner. And that accelerates your time to market even more.
How you can put this into practice today
Here are three things you can do today to start putting these ideas into practice.
- Start thinking about value value value, all the time. Only work on the most valuable things you can. Or, to put that another way, don’t work on things that aren’t valuable, even if they are cool or fun.
- Make sure your development team understands the value of what they’re working on. You can use the template I mention in this article to help: This New Template Helps You Write Better Product Requirements.
- When you talk to your execs about agile, don’t talk about agile, but about delivering value to market faster. Which results in higher revenue and more profits. Execs are typically much more interested in higher revenues and profits than they are in development and project management methodologies.
- “Value” by J.Lightning. Copyright (c) 2011 J. Lightning, Attribution-ShareAlike 2.0 Generic (CC BY-SA 2.0)
[…] three product rules of thumb which can determine if a product can be successful. There’s also my take on agile, ways to get over creative blocks, and how to […]
[…] practices are likely to help us achieve those goals? Well, an agile approach to development is often good for this. What do I mean by “agile?” I […]