Top Five Reasons You’re Wrong About Needing a Large Backlog

Most of these happen because people are confused about what, exactly, a backlog should be in an Agile environment.

The future will be awesome! And really messy too. Does it have to be that way?

In 1963, a U.S. President stated that he wanted to see, in that decade, a man walking on the moon. Did he deliver the specifications to the Saturn V moon rocket? Of course not. Do you think every week he received details on how hard the guidance team down in Huntsville was doing? Of course not. He stated a test, a high-level goal he wanted accomplished. He received periodic updates as new goals were accomplished: man living in orbit, capsules docking, and so forth. People followed along as each of these sub-goals were met, knowing that with each new capability the moon came closer.

Backlogs can be easy, intuitive, fun, and positive motivators for a team! Yay! Or they can be a micro-management death march. It all depends on what you’re willing to learn — and what you’re willing to un-learn.


Interested in learning more? I wrote the book on effective information management in your project. As it turns out, looking at your processes and workflows in terms of information management can help you figure out where things are going wrong. It’s called “Info-Ops”.


Follow the author on Twitter

July 4, 2018

Leave a Reply

Your email address will not be published. Required fields are marked *