- Paperback: 672 pages
- Publisher: Microsoft Press; 1 edition (July 12, 1996)
- Language: English
- ISBN-10: 9781556159008
- ISBN-13: 978-1556159008
- ASIN: 1556159005
- Product Dimensions: 7.4 x 1.6 x 9.2 inches
- Shipping Weight: 3 pounds (View shipping rates and policies)
- Average Customer Review: 92 customer reviews
- Amazon Best Sellers Rank: #149,642 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Rapid Development: Taming Wild Software Schedules 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you grow your business. Learn more about the program.
Frequently bought together
Customers who bought this item also bought
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
- 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.
Try the Kindle edition and experience these great reading features:
Read reviews that mention
There was a problem filtering reviews right now. Please try again later.
It had a lot of meat to the book.
I would recommend Team Lead's read this to give you some extra ideas about managing your development team.
made me pinpoint exactly all the faults those projects had. The
good thing about this book is that its complete. Some books cover
some areas and some others, but this covers all. For eg., if you
just read the first few chapters and decided to apply techniques
learnt to your project, you might not apply them correctly as you
you didn't read the whole book to get a complete picture of
This books is good for people working in startups. Developers
should also read this book so that they can help avoid mistakes
of managers/tech.leads in a fast-paced environment where things
can get easily missed.
Overall it was a nice easy read, but beware that it won't be very applicable early in your career.