The whole point of product management is to increase the product capabilities over time. Those capabilities will expand the customer base by offering new value. More customers means more revenue. That’s why the product vision for this release is so critical. That product vision requires strategic product leadership. The backlog is the tactical implementation of […]
In my recent project charter series, I said we need a product vision to drive the project charter effort so the customers can get this container of value. Who creates that product vision? The product leader. However, too many supposedly agile teams lack an effective product leader. Here’s what I’ve seen: A part-time product manager
As far as I can tell, all organizations have the appetite for more work than they have people or time to do that work. It does not matter if the organization is one person or thousands. We all want to accomplish more than we have people. That’s why we need a product vision to drive
I started this series by saying a team can create a useful project charter in less time than you think. So what prevents teams from doing so? Too often, the project is not ready. The team might be ready, but the project is not. In effect, the project starts with scarcity. (I used to think
So far, I’ve addressed how a project charter can help a team start a project fast and well. That’s why the project charter must clarify product vision, the various project risks, and product risks. And, it’s equally important to know what done means. If the team does not know how little they can do to
In Project Charter Part 2: Clarify the Project Driver, Boundaries, and Constraints for This Project, I explained how project risks can affect the team’s approach to the work. But project risks are not the same as product risks. Product risks are about the need for product innovation. The more innovation this product needs, the more
Does your team have an overarching goal for its work—a product vision? Too many teams do not. The whole point of a project is to deliver a useful product that satisfies its customers. I like to think about projects as a container of some product value. That means that a given release does not need
I’ve been working with several supposedly “agile” teams and their managers. Everyone knows their project is in trouble. And they have no idea what to do about it. The team members say, “We’re on a death march. We have no predictability. Everything takes longer than we think it will.” The managers say, “We have no
A colleague recently asked me how a team can deliver something useful in the next four to five weeks. “That’s all? Just four to five weeks?” I asked. Yes, that was all the time they had remaining. They’d worked on this product for a while, but that was the time they had left. This problem
I had so much fun recording a podcast with the Product Confidential people, Evie Brockwell and Michael Palmer. See the episode: The Essence of True Agility with Johanna Rothman. Check out the episode on Spotify and on Apple. Note: I do not use Spotify, nor do I use Apple, but I found the podcast in