Summary of Best-Practice Candidates
Each practice described in a best-practice chapter has been chosen for one of the following reasons:
Reduction of development schedules
Reduction of perceived development schedules by making progress more visible
Reduction of schedule volatility, thus reducing the chance of a runaway project
CROSS-REFERENCE
For more on the three kinds of schedule-related practices, see Attaining Rapid Development, Attaining Rapid Development.
Some of the best practices are described in Part I of this book, and those best practices are merely summarized in this part of the book.
You might ask, "Why did you ignore Object-Structured FooBar Charts, which happen to be my favorite practice?" That's a fair question and one that I struggled ...
Get Rapid Development: Taming Wild Software Schedules now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
