If you need to plan more often than once a quarter, how do you know how to replan? Instead of incurring the time and cost when you bring everyone together, consider the Product Value Team. (In past writing and presentations, I’ve called this the Product Owner Value Team. I am trying to change my term […]
One of my clients was trying—valiantly—to make their quarterly planning sessions work. They prepared, getting the big hotel room. They had plenty of supplies. The planning even went well. However, within two weeks, their plan had no relation to reality. That meant that for the next ten weeks, the product owners were “on their own.”
In Part 1, I wrote about thinking in feature sets so everyone could see smaller chunks of work. (If you can see them, you might be able to plan for smaller and deliver smaller.) In Part 2, I suggested smaller rolling waves than an entire quarter (two months, or preferably one month) so people could
In Part 1, I wrote about thinking in feature sets and how to quickly create a feature set of—with any luck—smaller features. That’s because features don’t arrive at the same rate and they change in value, during a quarter. Because features change in value and because some feature sets need to deliver value on a more regular
Many teams and organizations try to create one-quarter roadmaps. Here are the problems I see: Teams spend a ton of time estimating what they might do and then they select what will fit into a quarter. They feel or are asked to commit to all that work. The product managers and project portfolio managers depend on
Being an Agile Leader People tell me agile is past mainstream now, into the late adopters. I don’t buy it. Oh, agile has jumped the shark and made it into our vernacular. The result: I too often see agile as something the teams should do, without management using agile to improve the environment or their
As I write the program management book, I am struck by how difficult it is to estimate large chunks of work. In Predicting the Unpredictable and Manage It!, I recommend several approaches to estimation, each of which includes showing that there is no one absolute date for a project or a program. What can you do?
Go Small to Gain Momentum You’ve seen projects that start off great. They zoom along, delivering. And then something happens. They slow to a crawl. Sometimes, they get stuck so badly you decide to stop and declare victory (or defeat) and start all over. What can you do to make sure that doesn’t happen to
One of my program management clients is organizing a program and is having trouble thinking about a delivery model that fits their program. They are transitioning to agile and are accustomed to traditional releases. When I suggested they have someone representing deployment on their core team, that was an initial shock to their system, and
Do you have a product owner who doesn’t want to admit to technical debt? “Give me another feature! And another feature! Just keep giving me features! It’s feature time, baby!” Once a product owner has the heady feeling of seeing features one after the other, it’s difficult for that product owner to consider anything other