Poppendieck: Managing The Pipeline - The Diigo Meta page

• 06 Aug 09
  

  juha riissanen
  • The bottom line is that managing response time, or  time-to-market, is more efficient and more profitable than managing  utilization.  You need some slack to keep development and innovation  flowing.  As any good operations manager already knows, when work flows  rapidly and reliably through an organization, its efficiency and utilization  will be higher than in a organization jammed up with too much work.

  • Queuing theory gives us six  rules for reducing software development cycle time:

     
     
    1.  

       Limit work to capacity  

        
    2.  

       Even out the arrival of  work

        
    3.  

       Minimize the number of  Things-in-Process

        
    4.  

       Minimize the size of the  Things-in-Process

        
    5.  

       Establish a regular  cadence

        
    6.  

       Use pull scheduling  
• 08 Feb 09
  

  Yuval Yeret

  lean agile

• 05 Feb 08
  

  Julian Elve

  agile kanban poppendieck toc

• 18 Dec 07
  

  jonathan Belisle

  agile article management methodology process productivity lean development software

• 04 Oct 07
  

  fernando_cuenca

  management lean

• 

  patdavies40

  management lean

• 19 Sep 07
  

  Brian Drummond

  agile

• 04 Jul 07
  

  Drew Sudell

  Thinking about scheduling work ala queuing thory, with enough managemt speak to make managers think it makes sense. (Funny using OS scheduling analogs, while just as valid, does not work)

  scheduling pipeline project management

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.