Home >   >   > 

Software Project Survival Guide

지은이 Steve McConnell   |   출판사 Microsoft Press  |   발행일 1997년 10월 25일   |   언어 : English
클릭하시면 큰 도서이미지를 보실 수 있습니다.
판매가 35,000원27,300원 22%
마일리지 1% 350원
발행일 1997-10-25 | 중량: 0.52 kg | 사이즈: 18.9*23.4*2.4 cm
ISBN 1572316217 |  9781572316218
기타정보 원서 | 304쪽 | $ 24.99
배송비 무료배송
    정가, 판매가는 항공 운임료 포함
종합지수 1p 456 위
이 책의 번역서
  소프트웨어 프로젝트 생존 전략
Insight (인사이트) | Steve McConnell

Having worked in the software business as a tester, technical writer, programmer, client, consultant, and (most recently) manager, I've seen plenty of software projects crawl toward completion, overbudget, behind schedule, and defect-ridden. Consequently, I could share with you a long list of ways to fail when running a software project. Describing how to succeed is a much more difficult problem, and Steve McConnell's Software Project Survival Guide is the best attempt at a step-by-step guide I've run across.

Targeted at managers (from the top of organizations down through technical leads), McConnell's book provides a blueprint for a successfully managed project; the postulated development effort involves "3 to 25 team members and schedules of 3 to 18 months." At 288 pages, the book could be thinner, but it's easy enough to get through. McConnell has an engaging, conversational style, with a tinge of irreverent humor -- both of which make this book easy to approach. He uses little jargon and includes a comprehensive glossary, so nontechies should find it easy enough to follow.

McConnell moves quickly through a "survival test" to assess a project's chances of successful completion, then steps through the project life cycle, from preliminary planning to a postcompletion wrap-up. The approach he advocates is heavier on formal process than the industry norm, but McConnell makes a reasoned and (usually) compelling case for each component of the process, explaining how it increases the visibility of the project's progress and/or decreases a risk endangering the project's success. McConnell is careful to point out, however, that paperwork haphazardly pushed around for formality's sake will have the opposite of the desired effect, slowing the project's progress without improving quality. If you're trying to decide which bits of formal software-development practices to employ in your project, this is a good place to look for advice.

Software Project Survival Guide contains many examples of step-by-step procedural directions, which can be customized easily to suit your own project, and each chapter ends with a checklist of procedures to follow. Unlike many offerings from Microsoft Press, this book is relatively dense; graphics and figures are sparse and, when they do appear, generally serve a useful purpose, illustrating a point or backing up an argument.

I was disappointed by one aspect of Software Project Survival Guide: It assumes that you, the reader, can exercise complete control over the entire software-development process. While some managers do have such power, many of us have to work within limitations imposed by corporate politics and contractual obligations. Software projects often require a cooperative effort by two or more separate companies (or separate units within a large organization), each of which has a distinct culture, a natural tendency to hide the details of its operations from external scrutiny, and a deep resistance to the imposition of new software-development practices to conform to an outsider's expectations. This poses three challenges:

You need to facilitate interteam, cross-culture communication; for instance, to identify vital information and ensure that it is shared with and understood by all relevant parties. You and your counterpart(s) need to adapt your development practices to a mutually acceptable compromise position, and ensure that materials produced on both sides are compatible. You need to practice defensive risk management; you need to provide yourself with alternatives in case some component, whose development you do not control, is delivered late, with insufficient quality, or not at all (Murphy's Law usually applies).

To be fair, there's enough material there for three additional books (are you listening, Steve?).

While the Software Project Survival Guide hasn't unseated Fred Brooks' Mythical Man-Month as my candidate for best all-time book on software-project management, it's an honorable runner up. If you're an upper or middle manager in an organization that develops software, you should definitely read this book. If you're a technical lead or a developer, you should start with this book, then turn to McConnell's Rapid Development which provides lower-level and more detailed advice on how to run a successful development operation. I know that these two books have improved the way that I develop software. I hope that they will have a similar effect on you.
Acknowledgments vi
Preliminary Survival Briefing vii

I The Survival Mind-Set

1 Welcome to Software Project Survival Training
2 Software Project Survival Test
3 Survival Concepts
4 Survival Skills
5 The Successful Project at a Glance

II Survival Preparations
6 Hitting a Moving Target
7 Preliminary Planning
8 Requirements Development
9 Quality Assurance
10 Architecture
11 Final Preparations

III Succeeding by Stages
12 Beginning-of-Stage Planning
13 Detailed Design
14 Construction
15 System Testing
16 Software Release
17 End-of-Stage Wrap-Up

IV Mission Accomplished
18 Project History
19 Survival Crib Notes

Steve McConnell is a consultant to software-intensive companies in the Puget Sound area, including Microsoft. His primary focus has been on the development of mass-distribution commercial microcomputer software. In addition to more theoretical projects such as RAPID DEVELOPMENT and CODE COMPLETE, he has personally written more than 50,000 lines of production code in the last five years. McConnell earned a bachelor’s degree from Whitman College in Walla Walla, Washington, and a master’s degree in software engineering from Seattle University. He is a member of the IEEE Computer Society and the ACM.
등록된 서평이 없습니다.
꼼꼼한 재은 씨의 스위프트 실전편...
선택된 상품을 찜하실 수 있습니다. 선택된 상품을 바로구매 하실 수 있습니다.
회원평점   회원서평수 0
Steve McConnell 의 최근 저서
Professional 소프트웨어 개발
Microsoft Press 출판사의 신간
Solid Code

The Practical Guide to Defect Prevention
Harry Emil 저