Breaking The Quality-Speed Compromise - The Diigo Meta page

• 03 Feb 09
  

  Gerry

  Breaking The Quality–Speed Compromise

  lean

• 18 Apr 07
  

  synesthesia UK

  lean quality

• 29 Mar 07
  

  Steven Yamanaka

  by: mary poppendieck

  • But I generally
    find that the real problem is that the requirements were specified too
    early, when it was not really clear what was needed.  The way to reduce
    requirements churn is to delay the detailed clarification of
    requirements, moving this step much closer to coding.  This greatly
    reduces the change request queue, because you don’t need to change a
    decision that has not yet been made!
  • Many companies spend a great deal of time tracking, prioritizing, and
    fixing a long queue of defects.  Far better to never let a defect into
    the queue in the first place.
  • 1 more annotations...
  • • The way to get rid
      of the big delay at verification is to move testing closer to coding –
      much closer.

Would you like to comment?

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