Breaking The Quality–Speed Compromise
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
Bookmark History
Saved by 3 people (0 private), first by anonymouse user on 2007-03-29
- Gerry on 2009-02-03 - Tags lean
- Synesthesia on 2007-04-18 - Tags lean , quality
- Masaru on 2007-03-29 - Tags by: mary poppendieck
Public Sticky notes
The way to get rid
of the big delay at verification is to move testing closer to coding –
much closer.
Highlighted by masaru
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.
Highlighted by masaru
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!
Highlighted by masaru
Public Comment