Roadmap Integrity Process

If You Disclose Your Roadmap, Don’t Do It the Microsoft Vista Way

March 19, 2011
Vista Uncertainty - Square

Only you can decide whether your company must publicly disclose your product roadmap. But never disclose anything before you know what it really is, whether it works, whether customers even need it, or when you can deliver it.

Read the full article →

The Perfect Requirements Myth

March 18, 2011
Checklist

Many teams have a lot of angst about product requirements documents. Like the code your developers write, it will never be perfect. What can you do to reduce the angst?

Read the full article →

Estimating Business Impact…Simply

March 13, 2011
Finish Line

There’s a simple but powerful approach for estimating business impact: require the person asking for the project to estimate how many people will notice if the project is successful.

Read the full article →

Why Are We Doing This Project, Anyway?

March 13, 2011
Man running towards target

By ensuring that every software project is mapped to a specific business objective, you can have complete transparency on the “why” behind every software project.  You’ll also know how much you are investing – or not – in “innovation.”

Read the full article →

The Un-Innovation Trap

March 13, 2011
Innovation

Prioritizing projects by expected return on investment sounds like a good idea. But if that’s all you do, you will eventually end up in a place you probably don’t want to be.

Read the full article →

The Roadmap Integrity Process: An Overview

March 6, 2011
Project bubble chart organized into four quadrants.

What exactly is the Roadmap Integrity Process? In a nutshell, it’s a lightweight methodology for transforming a list of vague and often, half-baked ideas for new features, enhancements, and even engineering/architecture work, into a solid operating plan that accounts for execution risk.

Read the full article →

The Secret Sauce: Managing Uncertainty and Execution Risk

March 5, 2011
Uncertainty

Uncertainty is the missing link in how we plan and execute software projects. By asking one simple question for every project, long before you start, you can have a very good idea how many challenges you are likely to face along the way.

Read the full article →

Moving Bubbles Towards the Green

March 4, 2011
Moving to the Green

Inevitably, once you’ve classified projects according to business impact, cost, and execution risk, you’ll have projects that are too costly and/or risky. What do you then? Hint: your teams already know how to do it.

Read the full article →

When Business Goals Are Lost in Translation

March 1, 2011
Hey, at least they tried.

We’ve invested more effort into formulating business strategy and the best practices of building software than we have into figuring out how to accurately map one to the other. As as result, sometimes things are lost in translation.

Read the full article →

Roadmap Planning: The Brady Bunch Movie of Software

February 26, 2011
The Brady Bunch Movie

We’ve come a long way in how software developers write code, how QA verifies that it works correctly, and how software projects are managed. And once that’s done, it’s faster and cheaper than ever before to make software available to users. Yet there’s one aspect of creating software that hasn’t really changed.

Read the full article →