|Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
May the source be with you, but remember the KISS principle ;-)
Skepticism and critical thinking is not panacea, but can help to understand the world better
|How to Solve It|
|Programming Pearls||The True Believer||Lions' Commentary on Unix||K&R Book||Rapid Development||Winner-Take-All Politics||Military Incompetence|
|Alice's Adventures in Wonderland||Tao of programming||AWK book||Animal Farm||The Elements of Programming Style||Humor||Etc|
See the introduction to the series for more information
Rapid Development Taming Wild Software Schedules
by Steve C McConnell
Amazon Price: $28.00
Paperback - 647 pages (July 1996)
Microsoft Press; ISBN: 1556159005 ; Dimensions (in inches): 1.71 x 9.20 x 7.41
This book is essentially a companion book to update for The Mythical Man-Month and should be read after it. Steve McConnell repeats some ideas of Brooks and present some additional that became current since the publication of The Mythical Man-Month.
The author wrote another impressive book Code Complete A Practical Handbook of Software Construction, Second Edition, 2004
The level is slightly lower that in Brooks as Steve McConnell never lead the project of the size of OS/360.The nine page section entitled "Classic Mistakes Enumerated" is alone worth the price of the book 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:
ERCB Rapid Development - Dr Dobbes Review
The following excerpts are located on other Web sites and may or may not be available at any given time. The links are provided to our readers as a convenience only.
Practical Guide With Real Life Examples, August 3, 2003
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.
Organization of the book:
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):
Part 2 covers rapid development issues in greater detail.
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
The Best Practices listed are
The book has a very engaging style of writing...
All in all, a fully deserved five stars!
Outstanding Software Development process book, July 22, 2003
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.
Showed this to my former boss and he stole it from me...,
February 21, 2003
Very well written, easy to read with lots of advice to consider and follow.
Almost everything you need to face sucessfully any software project is covered. I have many other software management books and papers, and after reading them all I keep checking on this one as reference. From my point of view, this book is a must and a strong first buy for those who not only head a programmers group, but also for programmers itself.
A few years ago, and with that book recently bought, our programmer group stopped our manager (a non programmer) to take some "common" sense adjustments to a very cumbersome, badly designed and also delayed proyect (as most of his last important projects were): Wanted to add more people to the delayed project, force us to work round the clock to finish on time, abstract final users from validating our progress, and remove any more testing, leaving it to the end of the project.
After many hours discussing with him and reading him complete chapters of this book (and some other books), we decided to stop our work, took a day free to clear our minds, keep our team unchanged, sat with our users to reschedule delivery times and keep working from 9 to 6.
We didn't complete the work on time, but past projects were misscalculated by 50%, ours ended late by just 20%.
Now, on my new job where projects were (and are) delayed usually more than triple of time with a lots of non-payed extra hours ended on time or with little delays (company culture is very difficult here), within our budget and rarely needing extra time. Other teams on my company keep working forever on a always delayed work refusing to believe there is a better way to work here, to be at the end, looking to work somewhere else or leaving entire projects unfinished or needing a severe rewrite.
Our team uses this book (without approval from our systems director) and also two other titles that compliment the way we work (very well): Code Complete and Peopleware.
I do strongly recommend to get those books also.
Destroyed all misconceptions of the development process,
October 31, 2001
After digging around numerous sites, reading literally hundreds of reviews, and soliciting the opinions of fellow developers, I finally settled on ordering "Rapid Development" and one of the other books by the same author, "Code Complete".
All I can say is "holy cow". "Rapid Development" was delivered to my door around 3pm on a Saturday afternoon. I picked it up and right away read chapter 3 - "Classic Mistakes". The scenario presented in the chapter just about blew my mind; it detailed every issue I have ever come across in the development process that has stalled or killed a project. It was also well written with a dry, witty humor; a definate must for any technical book about typically dry subjects.
After reading that one chapter, I flipped back to the beginning of the book and read it all the way through. I didn't put the book down until midnight, and after I had, there were all sorts of ideas screaming through my head I could apply to my current engagements.
Managers and non-technical people will greatly benefit from this book too. Have you ever that manager who stands over your shoulder asking you how it's going, why you're doing something a certain way, or what's taking the project so long? Give this book to your manager and tell him to read Chapter 11, "Motivaton". Chapters 3 and 11 provided the proper explanations for the constant recurrance of certain software project issues ("Why are the programmers working twelve hours a day and the project never seems to get any closer to completion?" "What exactly is so hard about adding this one feature to the program that was never accounted for in the first place?" "If those programmers are such geniuses, why won't they share code or use each other libraries?") to persuade my company to buy this book for all developers and technical managers.
Never has a technical book provided me with so much insight and so much open-ended, thought-provoking detail. I was able to apply about a third of the principles described to about 90% of all the projects i've ever worked on without thinking for more then a minute or two. The other two thirds proved themselves when digging deeper into the various issues.
Blah. What a burst of hot air. I've personally never EVER written a review for a book (never enough time), but I just HAD to stop and give five stars to this one.
BUY THIS BOOK. AND BUY IT FOR YOUR MANAGERS. NOW.(...)I am THAT confident that it provide at least one improvement to the way you develop software, if not many.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2020 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to to buy a cup of coffee for authors of this site|
Last modified: March 12, 2019