Programming Books C Java PHP Python Learn more Browse Programming Books
Rapid Development (Developer Best Practices) and over one million other books are available for Amazon Kindle. Learn more
Qty:1
  • List Price: $35.00
  • Save: $12.21 (35%)
FREE Shipping on orders over $35.
Usually ships within 1 to 3 weeks.
Ships from and sold by Amazon.com.
Gift-wrap available.
Add to Cart
FREE Shipping on orders over $35.
Used: Very Good | Details
Sold by Protean Records
Condition: Used: Very Good
Comment: crisp, clean, and tightly bound. text unmarked. stamps on inside cover and page edge
Access codes and supplements are not guaranteed with used items.
Add to Cart
Have one to sell? Sell on Amazon
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Rapid Development: Taming Wild Software Schedules Paperback – July 12, 1996

ISBN-13: 978-1556159008 ISBN-10: 1556159005 Edition: 1st

Buy New
Price: $22.79
39 New from $6.65 178 Used from $0.08 1 Collectible from $9.98
Amazon Price New from Used from
eTextbook
"Please retry"
Paperback
"Please retry"
$22.79
$6.65 $0.08
Unknown Binding
"Please retry"

Free%20Two-Day%20Shipping%20for%20College%20Students%20with%20Amazon%20Student



Frequently Bought Together

Rapid Development: Taming Wild Software Schedules + The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) + Code Complete: A Practical Handbook of Software Construction, Second Edition
Price for all three: $81.02

Some of these items ship sooner than the others.

Buy the selected items together

NO_CONTENT_IN_FEATURE

Shop the new tech.book(store)
New! Introducing the tech.book(store), a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry. > Shop now

Product Details

  • Paperback: 680 pages
  • Publisher: Microsoft Press; 1 edition (July 12, 1996)
  • Language: English
  • ISBN-10: 1556159005
  • ISBN-13: 978-1556159008
  • Product Dimensions: 9.1 x 7.3 x 1.7 inches
  • Shipping Weight: 3 pounds (View shipping rates and policies)
  • Average Customer Review: 4.8 out of 5 stars  See all reviews (120 customer reviews)
  • Amazon Best Sellers Rank: #99,714 in Books (See Top 100 in Books)

Editorial Reviews

Amazon.com Review

I can hear some of you exclaiming, "How can you possibly recommend a book about software scheduling published by Microsoft Press and written by a consultant to Microsoft?!" Well, put aside any preconceived biases. This is a tremendous book on effective scheduling software development, and it drinks deeply from the wisdom of all the classics in the field such as Brook's Mythical Man Month -- and is likely well-informed by McConnell's experiences, good and bad, in Redmond.

The nine page section entitled "Classic Mistakes Enumerated" is alone worth the price of admission and should be required reading for all developers, leads, and managers. Here are some types of the 36 classic mistakes that McConnell describes in detail:

  • People Related Mistakes
    • Heroics
    • Adding people to a late project
    • Politics placed over substance (etc.)

  • Process Related Mistakes
    • Abandonment of planning under pressure
    • Planning to catch up later
    • "Code-like-hell" programming (etc.)

  • Technology Related Mistakes
    • Silver-Bullet syndrome
    • Overestimating savings from new tools or methods
    • Switching tools in the middle of a project (etc.)

I suspect that if you've ever been involved in software development, you winced after reading each of these nine points. And you will learn a great deal from the remaining 640 pages about concrete solutions.

My only substantive gripe: cheesy Powerpoint graphics. Nonetheless, this book is Very Highly Recommended.

About the Author

Steve McConnell is recognized as one of the premier authors and voices in the development community. He is Chief Software Engineer of Construx Software and was the lead developer of Construx Estimate and of SPC Estimate Professional, winner of Software Development magazine's Productivity Award. He is the author of several books, including Code Complete and Rapid Development, both honored with Software Development magazine's Jolt Award.


More About the Author

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

Customer Reviews

The time you will save after reading this book is worth much, much more than this book costs.
M. Kisialiou
The importance of this book is that it shows how to develop software with an aggressive schedule without compromising quality.
Harvey Sugar
This book is a must for development managers (those who manage software development projects)!
Doug Thews

Most Helpful Customer Reviews

82 of 84 people found the following review helpful By TrustNoOne on July 26, 1998
Format: 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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
62 of 65 people found the following review helpful By Abhinav Agarwal VINE VOICE on August 3, 2003
Format: 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.
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
24 of 25 people found the following review helpful By Tom O Bjorkholm on October 31, 1999
Format: 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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
25 of 27 people found the following review helpful By A Customer on December 31, 1997
Format: Paperback
I work for an Internet software development company, and I have made this book required reading for every project manager and technical lead in our company. McConnell's combination of conceptual knowledge, supported by hard facts, is a rare thing in software development "how-tos."
The best-practices section at the back of the book is an invaluable reference. His "bad" case studies depressed me sometimes -- mainly because they were too close to my own projects -- but the "good" ones have become the scripts for my presentations to clients. He has a way of capturing the essence of the atmosphere in a development shop, so the case studies feel as if they took place in your own office.
I would highly recommend this book to anyone whose job is managing the development process, whether that be in a technical lead or a project management position. Maybe if more people read this book and follow its guidelines, we could all stop working weekends.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
13 of 14 people found the following review helpful By M. Kisialiou on August 30, 2005
Format: Paperback
I have bought this book occasionally because of the well-known name of Steve McConnell. Originally I was confused by the title that seemed to indicate another super methodology that promised heavens. No need to say that I was skeptical about it. Do not look at the title, although this book emphasizes its value for the fast paced projects, it is THE BOOK on project management as a whole. In general, the book comprises practical knowledge of generations of project managers. Do not miss your chance to get it now easy in few days what took some people's life time to learn! Amidst lots of practical examples, you will also find an exciting style and lots of must-know suggestions on small, middle and large size projects. I believe that any project manager must read this book if she/he has not done it yet. In addition to what is covered in the book, the author provides lots of links and references in case you need to explore the area in more detail. The time you will save after reading this book is worth much, much more than this book costs.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Customer Images

Most Recent Customer Reviews

Search