Rapid Development [Paperback]

Steve McConnell (Author)

Product Details

• Paperback
• Publisher: Microsoft Press (February 1, 2003)
• Language: English
• ISBN-10: 0072850604
• ISBN-13: 978-0072850604
• Product Dimensions: 9.2 x 7.5 x 1.8 inches
• Shipping Weight: 3 pounds
• Average Customer Review: 4.8 out of 5 stars  See all reviews (115 customer reviews)
• Amazon Best Sellers Rank: #1,201,758 in Books (See Top 100 in Books)

More About the Author

I am CEO and Chief Software Engineer at Construx Software (www.construx.com). I've written Software Estimation, Code Complete, Rapid Development, Software Project Survival Guide, and Professional Software Development. I live in Bellevue, WA (near Seattle).

Customer Reviews

Most Helpful Customer Reviews

76 of 78 people found the following review helpful:

5.0 out of 5 stars Essential reading for programmers and their managers, July 26, 1998

By 

"stuartk3" - See all my reviews

This review is from: Rapid Development: Taming Wild Software Schedules (Paperback)

As a developer, you have been on that project.  The one that seems that it will never end. Requirements change daily, testing seems to discover new bugs faster than you can fix them, release dates come and go and noone seems to know when the project will be completed. If you're like me, maybe you thought that was just the way software projects were.

And then I read this book. Chapter 3 contains a case study of classic mistakes.  It sounded like every project I had ever worked on. Steve McConnell shows you how to avoid those mistakes, and how to leverage best practices in planning and development to achieve maximum predictability and control over your software schedule.  This should be required reading for all software project managers, technical leads and top management.  

While it's a long book, it lends itself to easy browsing. You can almost dip in at random and find some useful tip on how to improve your chances of bringing your project in on time and unde! r budget. But you'll want to read it straight through at least once. The last section of the book is devoted to individual Best Practices.  Each practice is explained along with its risks and benefits. Not all practices will be applicable to all projects, and the book guides you through when each is appropriate along with what practices it compliments.

61 of 64 people found the following review helpful:

5.0 out of 5 stars Practical Guide With Real Life Examples, August 3, 2003

By 

Abhinav Agarwal (Bangalore, India) - See all my reviews
(VINE VOICE)    (REAL NAME)   

This review is from: Rapid Development: Taming Wild Software Schedules (Paperback)

Steve McConnell's books have always displayed a remarkable degree of practicality and readability. This book is no different.

The author says at the outset the Purpose of the book is to answer issues about trade-offs. The author says that software can be optimized for any of several goals: lowest defect rate, lowest cost, or shortest development, etc... Software Engineering is then about achieving tradeoffs, and this is what this book is primarily about.
Because the book is so big, it has been broken into sections that can be read selectively and quickly. A short book would have oversimplified things to the point of uselessness.

Organization of the book:
Parts 1, 2 deal with the Strategy and Philosophy of rapid development, while part 3 covers Rapid develoment best practices

In chapter 3 the author talks about 'Classic Mistakes'. He calls them 'classic' and 'seductive' because they are so easy to make that they have been repeated in countless projects. The classic mistakes number 36 (though Steve M points out that a complete list could probably go on for pages and pages):
Undermined motivation, Weak personnel, uncontrolled problem employees, Heroics , Adding people to a late project , Noisy crowded offices , Friction between developers and customers , Unrealistic expectations , Lack of effective project sponsorship , Lack of stakeholder buy-in , Lack of user input , Politics placed over substance , Wishful thinking , Overly optimistic schedules , Insufficient risk management , Contractor failure , Insufficient planning , Abandonment of planning under pressure , Inadequate design , Planning to catch up later , Code-like-hell programming , Requirements gold-plating , Feature creep , Developer gold-plating , Push-me, pull-me negotiation , Research oriented development , Silver bullet syndrome , Overestimated savings from new tools or methods , Switching tools in the middle of a project , Lack of automated source-code control , Shortchanged quality assurance , Omitting necessary tasks from estimates , Shortchanged front end upstream activities.
He categorizes these classic mistakes into four sets : People related, technology related, product related, and process related.

Part 2 covers rapid development issues in greater detail.
Core issues like Estimation, Scheduling, Lifecycle Planning, etc.. are covered. `Soft' issues like Motivation, Teamwork, Customer Oriented Developmentare also covered.

Part 3 is a compendium of best practices. There is a summary table of the each best practice, and the efficacies, major risks, major interactions and trade-offs listed.

Some candidate best practices not included are getting top people
, Source Code Control, Requirements Analysis.. These are listed as fundamental to a software project.

The Best Practices listed are
JAD, Spiral Lifecycle Model, Theory W Management, Throwaway Prototyping, Staged Delivery, Voluntary Overtime, Miniature Milestones, Outsourcing, Reuse, User-Interface Prototyping, Change Board, Daily Build and Smoke Test, Tools Group.
As an example, Steve McConnel covers 'Inspections' stating the
chances of its long term success are excellent, it reduces schedule risk, its improvement in progress visibility is only fair, has no major risks, it can be combined with virtually any other rapid development best practice

The book has a very engaging style of writing...
Some quotes...
- Projects can look like a tortoise on valium to the customers, but as a rapid-development death march to the developers.
- The team ranks so low in the company that it has to pay to get its own team t-shirts.
- Rapid development isn't always efficient.
- Run every software project as an experiment (`Hawthorne Effect').
- If Las Vegas sounds too tame for you, software might be just the right gamble.
- The most common (and incorrect) definition of estimate is: `An estimate that has the most optimistic prediction that has a non-zero probability of coming true' - Tom DeMarco

All in all, a fully deserved five stars!

24 of 25 people found the following review helpful:

5.0 out of 5 stars Recommended reading -- Great reference, October 31, 1999

By 

Tom O Bjorkholm - See all my reviews

This review is from: Rapid Development: Taming Wild Software Schedules (Paperback)

The author of this book does not present "the one and only rapid development process". Instead the book presents in great detail over 20 good practices that are known to speed up development. The reader is expected to combine these practices to get a good combination for the current project.

The language in the book is smooth and the author really tries to explain in a simple and easy to understand way. I still needed a lot of time to read the book, simply because of the enormous amounts of information in the book.

The book includes a lot of statistical data. This is really great to have if you get into an argument with management about if the schedule is achievable.

The book is published by Microsoft Press. As I am very far from being a Microsoft fan, I was very sceptical at first. But the book is really great and applicable to all software development projects, including those on UNIX and embedded systems.