Roadmap Planning: The Brady Bunch Movie of Software

by Bill Bliss on February 26, 2011

in Roadmap Integrity Process

Remember 1995′s “The Brady Bunch Movie?”  It was based on the clever premise that the Bradys were forever stuck in the 1970′s while the rest of the world moved on.  The way we currently plan and prioritize software projects is kind of like that.

Thanks to the Internet, free/inexpensive yet high-quality open source software, and hosted SaaS products, there are more people and companies creating software than ever before.  These days, a significant percentage of small companies, and an even higher percentage of mid-sized and large companies, dedicate significant resources to creating and maintaining software.  (If you’re not sure whether your company does or not, here are a few clarifying questions – scroll to the bottom.)

With more and more people creating more and more software, you might think we’d be pretty good at creating it by now.  Well, in many ways that’s absolutely true:

  • The unit cost of computing power and storage declines every year.
  • Services such as Amazon AWS and Rackspace Cloud make it easy to deploy software applications “in the cloud” (and scale with customer demand) without committing to leasing or building costly data centers.
  • Software tools, platforms, and services are more powerful, cheaper, and easier to use than ever before.
  • Agile has revolutionized the way many software developers write code.  There is abundant high-quality training and coaching available for companies who want to start using Agile, and there is a broad selection of high-quality, inexpensive tools for managing an Agile development process.
  • QA has come a long way too.  QA is integrated into Agile, and many developers follow a best practice which keeps many defects from reaching QA in the first place.  Last but not least, there are many high-quality and often inexpensive or even free solutions for automating software tests.
  • Project management as a discipline has kept pace with Agile methodologies, and there’s even an organization which can certify project managers as Project Management Professionals.

Put another way, 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.

And yet…

There’s one aspect of creating software that hasn’t really changed.  Ever.
It’s figuring out what software to create in the first place.

It’s true. Everyone basically “rolls their own” planning process and everyone does it differently. There’s no equivalent of Agile (Agile, in fact, can make life more difficult for product managers). There are few, if any, best practices.  Some companies do it well, but I’ve found it’s something that many companies struggle with.

That’s why I founded Roadmap Integrity.  It’s time to throw away the bell bottoms and join the modern world.  I’ll be posting more on this topic over the next few months; for now, here are a few initial thoughts.

The takeaway? Software product planning—and the way we create product roadmaps—has been stuck in a time warp while software development, QA, and deployment/hosting is in the 21st century.  Maybe it’s time to change that.

Tweet this: @bill_bliss New post: Roadmap Planning: The Brady Bunch Movie of Software #prodmgmt

{ 3 comments… read them below or add one }

Todd Warren March 9, 2011 at 6:14 am

For us baby boomers, the brady bunch is an infinite source of ready analogies. See my related post on how to position products based on the Brady Bunch song I think the work you are doing here is terrific. Since Agile, and especially extreme, grew out of managing internal IT products, it often misses some of the marketing strategy elements essential in successful product development.


Bill Bliss March 9, 2011 at 6:48 am

Thanks Todd! I noticed you had written about the Brady Bunch too at about approximately the same time. What are the odds of that?

Glad you like it so far. More to come!


Alexia Marthoon January 9, 2014 at 1:55 am

Yeah its a very good article.The Agile retrospective is similar to that of the review meetings conducted to learn the do’s and avoid the pitfalls. Lessons are learned from real past experience and the team focuses on the necessary changes needed for in the subsequent iteration.As a project manager, I use Scrum in my projects. The Guide to Scrum Body of Knowledge by SCRUMstudy provided a complete reference for the Scrum project I am working with. It is a very good book and extremely readable. I really liked sections on risk and quality. The tools mentioned in the processes were very helpful. I highly recommend this book if you are planning to implement Scrum in your organization. You can go through the first chapter available on


Leave a Comment

Previous post:

Next post: