Index[A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [K] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W] [X] [Z] daily shipping data structures debugging milestones and working product and decision making defects avoiding backlogs of backlogs of build times and cost of fixing and time of discovery designing for reuse and detection of and cost of change detection vs. prevention of metrics for 2nd milestones and no broken windows practice and practices for preventing pragmatic practices for preventing 2nd preventing from reaching customers preventing vs. detecting 2nd 3rd prioritizing programming and code reviews and quality assurance and 2nd rearchitecture and root-cause analysis and ruthless testing for time spent fixing tools for tracking uncompromising attitude towards won't fix working product and Dell Computers design 2nd bottom-up discussions emphasis on extreme Extreme Programming and for reuse for testability frequent meetings in guiding principles in patterns in practices for rearchitecture and refactoring and reviews simplicity in top-down vision in deterministic programs discipline 2nd Extreme Programming and disruptive technologies diversity documentation barely sufficient code reviews and dangers of excessive design and in plan-driven development source code updating doxygen dynamic systems development method (DSDM) |