I’m working on the program management book, specifically on the release planning chapter. One of the problems I see in programs is that the organization/senior management/product manager wants a “commitment” for an entire quarter. Since they think in quarter-long roadmaps, that’s not unreasonable—from their perspective. There is a problem with commitments and the need for […]
Many product owners have a tough problem. They need so many of the potential features in the roadmap, that they feel as if everything is #1 priority. They realize they can’t actually have everything as #1, and it’s quite difficult for them to rank the features. This is the same problem as ranking for the
We encounter problems all the time. Some we can resolve on our own in a couple of minutes. Some take more time, and/or we can’t resolve them alone. What do you do then? I’ve had a policy for about twenty years for when I become stuck. If I’m stuck for more than twenty minutes, it’s
As I work with more clients on their programs, I see that what might work for a product owner for a team does not work for a program. In a program, if the product owner is shortsighted, does not take advantage of agile/lean for updates, and does not have small features, the program loses momentum.
Agile product leaders (product managers, product owners, and business analysts) all have one goal: How do I support the team in their quest to deliver better and faster? Product leaders do this by helping the team plan with minimums, and continually replan. These two workshops help you do that. I offer two versions: for teams,
Creating Trustworthy Estimates Do the people who ask you for estimates trust your estimates? It’s difficult to build trustworthy estimates. Here are three tips you can try for estimates that work for you, not against you. Tip #1: Never provide a single-point estimate. When people ask me for an estimate, I provide a percentage confidence
Several years ago, I had a senior VP as a client. He wanted his managers to work as more of a team. He thought they were not working together for the good of the company. I asked him why he thought that. “When they estimate, they don’t work together on an estimate. They each estimate
I spoke with a new manager, Drew, the other day. His days are full. He’s got tons of meetings. He tries to provide feedback and coaching to his team members, but he has crises up the wazoo. Drew asked for coaching: “I have way too much to do. I need to learn how to manage
My column is up on projectmanagement.com. It’s called Is Agile Working for Your Project? I hope you enjoy it.
A client asked me to do an assessment. He wasn’t sure agile was working for their teams. The standup meetings felt like micromanagement. People were on several projects, so they didn’t meet their commitments. The project manager had to translate the project’s progress and status to Gantt charts. Worst of all, people went through the