Do you use schedule or tracking tools to predict the future? None of them can predict the future. Worse, too many of them hide the past, especially the recent past. A schedule or tracking tool can only predict one thing: the first possible date you cannot prove you cannot finish the project/story by. Let me […]
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
Let me set the context for this post about the project charter: By now, the team knows what it has to accomplish because they have a product vision. The next question is: How will the team manage their risks to achieve those outcomes? That’s where I recommend a team define its project driver, up to
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
Does your team have a project charter so they know what to do for this project? I see too many teams try to start work without one. That leads to feature factories, apparently random work that does not add value, or worse, a product that’s partly done in too many areas. Teams start without project
This is Johanna Rothman’s August 2025 Pragmatic Manager newsletter. The Unsubscribe link is at the bottom of this email. Amy, a project manager, said, “With all the changes going on, no one is quite sure of their next steps. The portfolio team is stuck because they can’t predict for a year anymore. The product leader
Is your team ever surprised by how long things take? Do you hear things such as: Team members say, “I’ve been waiting for code review for more than 2 days.” (See Measure Cycle Time, Not Velocity to see the various durations for solo, cooperative, and collaborative work. Cycle time is a team-based measure of feedback
In a recent conversation, an unemployed agile coach asked, “What’s the point of a project manager, anyway?” Here’s what effective project managers do: They create the environment for the team to succeed. Here’s how effective project managers start: If the team does not yet have a project charter with the product goal, they facilitate or
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