• About me

    JensI have been working as a software consultant for more than 11 years. Because of that I am an eager supporter of lean principles and agile methods.

  • Recent Posts

  • Recent Comments

    • lazer epilasyon: A blog post was really useful, you can not find the information sought in a lot of places I’ve...
    • one minute left: not be published) (required) Website. Subscribe to comments feed. What do the extreme left and...
    • joseph pelrine: I will have to watch that as I’m a big fan of his because of the unique perspectives he brings....
    • Code Monkeyism: time. Too many developers on the other hand lead to communication overhead and get ineffective says...
    • Websites tagged "scrum" on Postsaver: - Speaking at Nordic Scrum Forum saved by speechjon2009-09-03 - Drury snaps...
  • Archives

  • Blogroll

  • Meta

How do we approach the problem with overwhelmingly large backlogs? The answer is simple. Make sure the backlog is prioritized first and then simply throw away the lower half. It sounds controversial but it’s all about limiting work to capacity. Having too large backlogs means that you are building inventory and inventory is waste that eventually degrades and becomes obsolete.

Instead adapt your backlog to your output capacity. If you are afraid of loosing important features in this process you need not worry, if they are important they will eventually reappear. Having a smaller backlog also makes you more responsive to new features and it consumes less resources.

These conclusions can be drawn by studying Lean Manufacturing Principles, which partially originates from queuing theory.

Something to say?

Bloggtoppen.se