About the Blog

  • Software is our business, and perfecting the art and science of delivering it is our mission. The contributors to this blog are passionate about the impact that great teams and good software can have on an organization’s bottom line. They bring decades of experience designing, developing and delivering great software, and each is playing a critical role in Borland’s own transformation.

Blogging Authors

« Using a Repository for Agile Requirements Collaboration | Main | Staffing Agile Teams - What to Look for in a Team Member »

January 31, 2009


Feed You can follow this conversation by subscribing to the comment feed for this post.

Ian Buchanan

Your groupings are all useful. However, there is probably 1 more very important category: what we won't do. Lining up a very long list may set unrealistic expectations with the customer (or customers). As long as they see their item in the backlog, they will expect it. The reality is that many things near the bottom will never be done because there will be new items that keep pouring in at higher priority. Therefore, saying "no" to low priority items is an important (but often overlooked) technique for keeping backlogs manageable.

The comments to this entry are closed.