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 […]
I’ve been talking with a very sharp leader about how that person uses the ideas of risk and technical debt. I’m paraphrasing, but the leader said something like this: “We realize we need to incur some technical debt. So we explain that we choose to include the debt as part of our risk mitigation. That’s
Your team says they use Scrum in two-week iterations. And, in order to “finish” everything inside the timebox, you don’t do any of these things: Refactor to simplify the code or the tests. Create automated tests. Use formal acceptance criteria on a story or for the iteration or the project. That means you have work
In a conversation about product quality, the product owner said, “If the testers found the problems faster, we would be done faster.” The tester said, “If the developers didn’t put so many problems in, we’d be done by now.” The developer said, “If you didn’t pressure me so much, I could have done a better
Back when I was a manager, my senior management wanted to separate the “new” work from the “maintenance” work. I suggested that every new line after the first line of code was maintenance. The managers poo-poohed me. My concern: How would the “new” developers learn from their mistakes? I lost that discussion and I managed
I spoke with a project manager recently. She told me her story. I used to facilitate project teams as a project manager. Why a project manager? Because the project had a beginning and an end. We had (and still have) too many products to keep the same teams on them for a long time. For
Part 1 was about seeing the value in the various projects. I called the value stream a product so that people would think about who would use it and why. I suggested that we stop work on specific products when you have more products than teams. That would allow you to work on other projects
I listened to The Ultimate Metric: Identifying the Right Problems to Solve. The guest, Janelle Klein, said: Technical debt is not a loan I thought that was brilliant. She went on to explain that when we talk about “debt” managers think they have dials to manage the debt. Uh oh. Wrong. When managers think in
If you read my Three Alternatives to Making Smaller Stories, you noticed one thing. In each of these examples, the problem was in the teams’ ability to show progress and create interim steps. But, what about when you have a “wicked” problem, when you don’t know if you can create the answer? If you are
When I was in Israel a couple of weeks ago teaching workshops, one of the big problems people had was large stories. Why was this a problem? If your stories are large, you can’t show progress, and more importantly, you can’t change. For me, the point of agile is the transparency—hey, look at what we’ve