Agile Zone is brought to you in partnership with:

Mike Cohn is a consultant and trainer who specializes in helping companies adopt and improve their use of agile processes and techniques in order to build extremely high performance development organizations. He is the author of Succeeding with Agile, Agile Estimating and Planning, and User Stories Applied for Agile Software Development. He can be reached through his website at http://www.mountaingoatsoftware.com. Mike is a DZone MVB and is not an employee of DZone and has posted 21 posts at DZone. You can read more from them at their website. View Full User Profile

A New Artifact – The Long-Term Product Backlog

05.06.2011
| 908 views |
  • submit to reddit

The weather turned nice about two weeks ago, which meant it was time for spring cleaning about the Cohn home, affectionately known as the Cohnderosa (which will only mean something if you’re old enough to remember “Bonanza”). While washing the windows around the outside of the house I had plenty of time to think about spring cleaning I’d also just helped a couple of clients with–we cleaned up their product backlogs.

The Long-Term Product Backlog

In order to clean up the product backlog, I want to introduce you to a new Scrum artifact–the Long-Term Product Backlog. The Long-Term Product Backlog is maintained by the product owner and is usually round, black and sits next to or under the product owner’s desk. Left unattended, a product backlog can become large and hard to work with. If your backlog has reached this point, take some time to do some spring cleaning—review the backlog and delete / throw away user stories that you can finally admit you’re never going to get to.

Some product owners or teams feel this is an admission of failure. It’s not. In most cases it’s an admission of success–we’re throwing away feature ideas that we once thought important because since writing them down we’ve discovered even more important features. So celebrate the fact that you’ve got newer, bigger, better feature ideas and delete the less valuable ones from your product backlog.

If permanently deleting such ideas is too big of a step, perhaps you really do want to introduce a new artifact into your process. Create a spreadsheet and paste the user stories there for safe keeping. Or print a report from your product backlog tool and file the report somewhere safe just in case. In my experience, though, you won’t miss them. And just like the bright new view through the windows of the Conderosa, you’ll be able to see the rest of your product backlog much more clearly.

References
Published at DZone with permission of Mike Cohn, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Tags:

Comments

Muhammad Faiz replied on Fri, 2012/04/13 - 8:44am

In a project some years ago, we struggled with some features that kept popping up, being discussed, then shuffled around priority-wise. In the end, I added a thick black line by the bottom of the Excel sheet where we kept our (quite short) product backlog. When needed, we placed features “below the black line”, to indicate that they were permanently considered “out” – in order to save some time discussing them _once_again_. Thanks for the post!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.