I work with many teams that have extensive product backlogs. Each iteration has a backlog of more items than the team can typically finish. Worse, some organizations want many quarters’ worth of backlogs, as in the image in this post. There are several problems with long and extensive backlogs: They tend to be wishlists of […]
At a recent conference, one of the attendees, Dave (not his real name), said, “I really liked some of your answers at the panel this morning. How much do you charge to speak?” I said, “Thanks. I charge based on several factors—” He interrupted me and said, “No, it’s an hour—or maybe, a half-day max.
I’m excited to be part of TheAgileNetwork.com. That’s where people with significant expertise in agility gather to share their expertise. While frameworks and methods are useful for some people, my clients find them of limited value. My clients—and I bet many of you, my readers—need practical and pragmatic ideas rather than a specific agile framework
I discussed how to calculate the Costs of Delay in the previous three posts, and then offered an example in Part 3. Notice that the example uses cycle time or how the team feels about the remaining time to think about the value in order to rank the work. (The links to all the posts
Ranking work, whether it’s for the backlog, a roadmap, or the portfolio, sometimes feels like throwing darts and hoping for the best. But especially if there’s too much work and a lot of WIP, we have a tool for clarifying that ranking—the Cost of Delay. It does require counting the number of people and easy
In Part 1, I explained the various Costs of Delays with this image: I explained how to calculate the salary costs in Part 1. Now, it’s time to calculate/assess Costs 2, 3, and 4 to decide on the most valuable work. (If you have Manage Your Project Portfolio, there’s an entire section about calculating and
If you’re like my clients (or me!), you have too much work to do. (I’m beginning to think “too much work” is the norm.) But how do you decide what to do first, second, and third? And never? I use Cost of Delay. (I’ve written about how to see the various Costs of Delay, especially
This is the June 2024 Pragmatic Manager Newsletter, from Johanna Rothman. The Unsubscribe link is at the bottom of this email. A newsletter reader asked me this question: Are there common reasons that projects fail? There are. These reasons aren’t just for product development projects, but for any effort that has some risk and requires
Do you have an overstuffed backlog the way Jenny did in Create More Success: How to Say No to “Everything” to Say Yes to What’s Necessary Now? I offered “now” advice in that newsletter. But what about the future? How can you prevent an overstuffed backlog, roadmap, or all those great ideas from interrupting your
In How Centralization Decisions Create Friction, Increase Cycle Time, and Cost Money, Part 1, I discussed how removing support staff for departments and managers created longer cycle times. (And sometimes, increased friction so much that people could not easily do their jobs.) Removing those support staff was one indication the companies fell into the Economies