Help Managers Visualize Their Problems

I’ve been working with several managers at organizations large and small, who want to capitalize their software “earlier.” These managers have some strongly-held beliefs about the people: People are resources Resources can multitask on several projects at a time If “headquarters” does the difficult work, you can move the “grunt” work to lower wage areas …

Estimation Article Posted: When to Estimate and When Not to Estimate

Do estimates make you slightly crazed? Maybe you want to roll your eyes at the organization’s confusion between your estimate (guess) and a commitment. You’re not alone. I wrote an article about estimation, How to give IT project estimates—and when not to estimate at all. If you’ve ever struggled with estimating work, give it a read. …

Questions to Ask Before Estimating an Agile Program Posted

My most recent article on projectmanagement.com is 3 Questions to Ask Before Estimating an Agile Program. In both Create Your Successful Agile Project and Agile and Lean Program Management, I talk about the reality of estimates in most settings. The question is what kind of an estimate does your project or program need? I’m not opposed to …

Alternatives for Agile and Lean Roadmapping: Part 7, Summary

Let me summarize what I’ve been talking about in these posts. The problem I’m seeing is that too many teams and organizations plan too much in too much detail too soon. Instead of architectural BDUF (Big Design Up Front), it’s project planning as BDUF. They expect one single person (a product manager or a product …

Alternatives for Agile and Lean Roadmapping: Part 6, Managers Want Commitments

You’ve started thinking in feature sets. Maybe you’ve experimented with  rolling wave plans inside one quarter, so you can change and replan as you need to support your project or program. You’ve discussed flow-based roadmapping as a way to create MVPs and MVEs, release smaller value more often so you can make better decisions. You …

Alternatives for Agile and Lean Roadmapping: Part 5, the Product Value Team

If you need to plan more often than once a quarter, how do you know how to replan? Instead of incurring the time and cost when you bring everyone together,  consider the Product Value Team. (In past writing and presentations, I’ve called this the Product Owner Value Team. I am trying to change my term …

Alternatives for Agile and Lean Roadmapping: Part 4, Resilience, Prediction, & Feedback

One of my clients was trying—valiantly—to make their quarterly planning sessions work. They prepared, getting the big hotel room. They had plenty of supplies. The planning even went well. However, within two weeks, their plan had no relation to reality. That meant that for the next ten weeks, the product owners were “on their own.” …

Alternatives for Agile and Lean Roadmapping: Part 3, Flow-Based Roadmapping

In Part 1, I wrote about thinking in feature sets so everyone could see smaller chunks of work. (If you can see them, you might be able to plan for smaller and deliver smaller.) In Part 2, I suggested smaller rolling waves than an entire quarter (two months, or preferably one month) so people could …

Alternatives for Agile and Lean Roadmapping: Part 2, Rolling Wave Planning Inside One Quarter

In Part 1, I wrote about thinking in feature sets and how to quickly create a feature set of—with any luck—smaller features. That’s because features don’t arrive at the same rate and they change in value, during a quarter. Because features change in value and because some feature sets need to deliver value on a more regular …