Rapid Development (Developer Best Practices) and over one million other books are available for Amazon Kindle. Learn more
CDN$ 29.58
  • List Price: CDN$ 46.95
  • You Save: CDN$ 17.37 (37%)
Usually ships within 1 to 3 weeks.
Ships from and sold by Amazon.ca.
Gift-wrap available.
Quantity:1
Add to Cart
Have one to sell?
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 – Jul 12 1996


Amazon Price New from Used from
Kindle Edition
"Please retry"
Paperback
"Please retry"
CDN$ 29.58
CDN$ 27.34 CDN$ 4.61

Join Amazon Student in Canada



Frequently Bought Together

Rapid Development: Taming Wild Software Schedules + Code Complete + The Pragmatic Programmer: From Journeyman to Master
Price For All Three: CDN$ 95.55

Some of these items ship sooner than the others. Show details

  • Usually ships within 1 to 3 weeks.
    Ships from and sold by Amazon.ca.
    FREE Shipping. Details

  • Code Complete CDN$ 33.22

    In Stock.
    Ships from and sold by Amazon.ca.
    FREE Shipping. Details

  • The Pragmatic Programmer: From Journeyman to Master CDN$ 32.75

    In Stock.
    Ships from and sold by Amazon.ca.
    FREE Shipping. Details


Customers Who Bought This Item Also Bought

NO_CONTENT_IN_FEATURE

Product Details

  • Paperback: 674 pages
  • Publisher: Microsoft Press; 1 edition (July 12 1996)
  • Language: English
  • ISBN-10: 1556159005
  • ISBN-13: 978-1556159008
  • Product Dimensions: 23.2 x 18.4 x 4.4 cm
  • Shipping Weight: 1.3 Kg
  • Average Customer Review: 4.8 out of 5 stars  See all reviews (92 customer reviews)
  • Amazon Bestsellers Rank: #97,188 in Books (See Top 100 in Books)
  • See Complete Table of Contents


Inside This Book (Learn More)
First Sentence
THE PRODUCT MANAGER TOLD ME he wanted to build a product right for a change. Read the first page
Explore More
Concordance
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:

What Other Items Do Customers Buy After Viewing This Item?

Customer Reviews

4.8 out of 5 stars
Share your thoughts with other customers

Most helpful customer reviews

Format: Paperback
Learn about project scheduling, risk management, and peopleware issues in this well written book. The example scenarios re-enforce the ideas presented throughout the book.
In the end, you'll walk away with a solid understanding of the project development cycle.
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.
By T. Hiltbrand on April 5 2004
Format: Paperback
I found this book to be enlightening on so many issues. I bought it thinking that it was touting a new methodolgy that would save the world from failing IT projects and found that it was a general summary of many things that will increase the efficiency and effectiveness of your IT team. It is very insightful and an overall good read.
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.
Format: Paperback
I'm a big fan of eXtreme Programming (XP) so I was particularly interested in reading this book to see if I could pick up some ideas and concepts different from that of XP. I was quite suprised to see many of the concepts and best practices McConnell presents in this book are very consistent with XP's practices. I also like how McConnell gives lots of references for his claims. He gives plenty of convincing data and supporting arguments to show what many of us already know yet many managers refuse to believe. Things like mandatory overtime can make productivity go down, the importance of moral, why managers can't control all the variables of a SW project (cost, schedule, & product). Overall this book is a great read and I really believe if everyone followed this book's best practices, especially 40 hour work week and honest scheduling, the entire SW industry would be much better than it is today.
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.
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 ›
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.
Format: Paperback
Unrealistic schedules are the bane of the software world's existance. In a world of "the quick and the dead" and "first mover advantage" achieving the unachievable seems to be a way of life in the industry. Steve McConnell takes a level headed approach at this crucial problem.
Steve looks at 3 dimensions of the problem - people, process and technology. In the spirit of haste, lots of mistakes are made. Steve then covers many of the techniques available, and identifies their impact to schedule, risk, and other factors. This isn't just a "how I learned how to do it" - it's backed up by hard research on what works, and what doesn't. Invaluable information for anyone serious about improving their ability to survive in such a hypercharged environment.
Ultimately, there is no silver bullet to this problem. Telling your project manager to read this book won't solve world peace. But carefully applying the tools and techniques listed will do you a world of good.
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.
Format: Paperback
If there is any one book that all developers and would-be project managagers should have - it's this one. Steve McConnell's writing style alone makes this an enjoyable read. Filled with tons of empirical data that is germane for any software project, this book is a tremendous resource. Having developed software professionally for over ten years now, I still find this book my favorite. Even though it was published in 1996, all of the material contained therein is still very pertinent to today's N-tier software development projects.
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.
By Jessica Sant on April 18 2003
Format: Paperback
Despite the fact that this book is over 5 years old -- its still an excellent resource. I used this book in my Software Project Management course for my Master's Degree and can definiltly see myself using it in the future at work.
The book clearly explains the many risks and strategies involved in Rapid Development. The author uses anecdotes and examples effectively to illustrate his points. Many of the ideas build on top of each other to reinforce good methodologies for a project manager to follow -- but the book can also be read randomly (a chapter here, a chapter there).
This is a great resource from a developer's perspective too -- it gives you the ammunition to debate with an untrained, unknowledgable, misinformed or mislead project manager who's asking WAY too much and doesn't even realize it. I think anyone involved in the software engineering process will be able to take away a lot of knowledge from this book.
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.

Product Images from Customers

Search


Feedback