Software Project Survival Guide
by Steve McConnell
On This Page
Description
Equip yourself with SOFTWARE PROJECT SURVIVAL GUIDE. It's for everyone with a stake in the outcome of a development project--and especially for those without formal software project management training. That includes top managers, executives, clients, investors, end-user representatives, project managers, and technical leads. Here you'll find guidance from the acclaimed author of the classics CODE COMPLETE and RAPID DEVELOPMENT. Steve McConnell draws on solid research and a career's worth of show more hard-won experience to map the surest path to your goal--what he calls "one specific approach to software development that works pretty well most of the time for most projects." Nineteen chapters in four sections cover the concepts and strategies you need for mastering the development process, including planning, design, management, quality assurance, testing, and archiving. For newcomers and seasoned project managers alike, SOFTWARE PROJECT SURVIVAL GUIDE draws on a vast store of techniques to create an elegantly simplified and reliable framework for project management success. So don't worry about wandering among complex sets of project management techniques that require years to sort out and master. SOFTWARE PROJECT SURVIVAL GUIDE goes straight to the heart of the matter to help your projects succeed. And that makes it a required addition to every professional's bookshelf. show lessTags
Recommendations
Member Reviews
I really enjoyed this, possibly the most concise and short of McConnell's software design and project management tomes. I found I labeled for reference many spots in this work: Customer's Bill of Rights, Survival Test Score (cf., Raleigh Model), a good overview of required elements of a software process around requirements. Among the points I found interesting was the research into the ineffeciency of open work bays vis-avis the need for continued focus by developers.
I also liked the broad view of vision documents and post mortems as this should be a broadly defined and controlled process, too. In there are such realistic caveats as "plan should not assume the team will work overtime" and support for scientific estimation processes and show more coding standards although I think he has left reality with "The best coding standards are .. less than 25 pages". show less
I also liked the broad view of vision documents and post mortems as this should be a broadly defined and controlled process, too. In there are such realistic caveats as "plan should not assume the team will work overtime" and support for scientific estimation processes and show more coding standards although I think he has left reality with "The best coding standards are .. less than 25 pages". show less
Ratings
Members
- Recently Added By
Author Information
15 Works 5,228 Members
Steve McConnell is CEO and chief software engineer at Construx Software, where he oversees their software engineering practices, teaches classes, and writes books and articles
Series
Belongs to Publisher Series
Common Knowledge
- Canonical title
- Software Project Survival Guide
- Original publication date
- 1997-10-22
Classifications
- Genres
- Technology, Business, Nonfiction, General Nonfiction
- DDC/MDS
- 005.10684 — Computer science, information & general works Computer science, knowledge & systems Software development, software, data, security Software development modified standard subdivisions Organizations and management Management Executive
- LCC
- QA76.76 .D47 .M394 — Science Mathematics Mathematics Instruments and machines Calculating machines Electronic computers. Computer science Computer software
- BISAC
Statistics
- Members
- 547
- Popularity
- 53,909
- Reviews
- 1
- Rating
- (3.92)
- Languages
- English, French
- Media
- Paper, Ebook
- ISBNs
- 5
- UPCs
- 1
- ASINs
- 2
