Software Inventory by Joel Spolsky
One easy way to limit the size of the backlog is to let the community itself vote on which bugs and features you should be working on, then add a little editorial selection and take the top (n) to work on. That's what we do at Stack Exchange, anyway:<p><a href="http://meta.stackoverflow.com/?tab=bugs" rel="nofollow">http://meta.stackoverflow.com/?tab=bugs</a>  
<a href="http://meta.stackoverflow.com/?tab=requests" rel="nofollow">http://meta.stackoverflow.com/?tab=requests</a><p>I find that the community appreciates being involved in these decisions, and often (but not always†) has good ideas of what you should be prioritizing and what issues are true pain points.<p>† <a href="http://www.codinghorror.com/blog/2012/02/listen-to-your-community-but-dont-let-them-tell-you-what-to-do.html" rel="nofollow">http://www.codinghorror.com/blog/2012/02/listen-to-your-comm...</a>