《软件工程的秘密：软件开发项目为何失败》

SOFTWAREPROJECTSECRETSWHYSOFTWAREPROJECTSFAIL5505FM.qxd7/22/0511:49AMPagei5505FM.qxd7/22/0511:49AMPageiiSOFTWAREPROJECTSECRETSWHYSOFTWAREPROJECTSFAILGeorgeStepanek5505FM.qxd7/22/0511:49AMPageiiiSoftwareProjectSecrets:WhySoftwareProjectsFailCopyright©2005byGeorgeStepanekLeadEditor:DominicShakeshaftTechnicalReviewer:DavidPutnamEditorialBoard:SteveAnglin,DanAppleman,EwanBuckingham,GaryCornell,TonyDavis,JasonGilmore,JonathanHassell,ChrisMills,DominicShakeshaft,JimSumserAssociatePublisher:GraceWongProjectManager:SofiaMarchantCopyEditManager:NicoleLeClercCopyEditor:LizWelchAssistantProductionDirector:KariBrooks-CoponyProductionEditor:EllieFountainCompositor:DinaQuanProofreader:PatrickVincentIndexer:CarolBurboArtist:KineticPublishingServices,LLCInteriorandCoverDesigner:KurtKramesManufacturingManager:TomDebolskiLibraryofCongressCataloging-in-PublicationDataStepanek,George.Softwareprojectsecrets:whysoftwareprojectsfail/GeorgeStepanek.p.cm.ISBN1-59059-550-51.Computersoftware--Development.2.Projectmanagement.I.Title.QA76.76.D47S7332005005.1--dc222005019810Allrightsreserved.Nopartofthisworkmaybereproducedortransmittedinanyformorbyanymeans,electronicormechanical,includingphotocopying,recording,orbyanyinformationstorageorretrievalsystem,withoutthepriorwrittenpermissionofthecopyrightownerandthepublisher.PrintedandboundintheUnitedStatesofAmerica987654321Trademarkednamesmayappearinthisbook.Ratherthanuseatrademarksymbolwitheveryoccurrenceofatrademarkedname,weusethenamesonlyinaneditorialfashionandtothebenefitofthetrademarkowner,withnointentionofinfringementofthetrademark.DistributedtothebooktradeworldwidebySpringer-VerlagNewYork,Inc.,233SpringStreet,6thFloor,NewYork,NY10013.Phone1-800-SPRINGER,fax[phone],[e-mail],[e-mail],orvisit“asis”basis,withoutwarranty.Althougheveryprecautionhasbeentakeninthepreparationofthiswork,neithertheauthor(s)norApressshallhaveanyliabilitytoanypersonorentitywithrespecttoanylossordamagecausedorallegedtobecauseddirectlyorindirectlybytheinformationcontainedinthiswork.5505FM.qxd7/22/0511:49AMPageivToErica,withoutwhomIwouldnotbewhoIamtoday5505FM.qxd7/22/0511:49AMPagevContentsataGlanceABOUTTHEAUTHOR...............................xiiiABOUTTHETECHNICALREVIEWER......................xvACKNOWLEDGMENTS..............................xviiPARTIWHYSOFTWAREPROJECTSFAIL...CHAPTER1INTRODUCTION..........................3CHAPTER2WHYSOFTWAREISDIFFERENT................7CHAPTER3PROJECTMANAGEMENTASSUMPTIONS..........23CHAPTER4CASESTUDY:THEBILLINGSYSTEMPROJECT........51PARTII...ANDHOWTOMAKETHEMSUCCEEDCHAPTER5THENEWAGILEMETHODOLOGIES.............65CHAPTER6BUDGETINGAGILEPROJECTS.................97CHAPTER7CASESTUDY:THEBILLINGSYSTEMREVISITED......115CHAPTER8AFTERWORD..........................131vi5505FM.qxd7/22/0511:49AMPageviAPPENDIX:THEAGILEMANIFESTO.......................133GLOSSARY.....................................135BIBLIOGRAPHY...................................143INDEX........................................151vii5505FM.qxd7/22/0511:49AMPageviiContentsABOUTTHEAUTHOR...............................xiiiABOUTTHETECHNICALREVIEWER......................xvACKNOWLEDGMENTS..............................xviiPARTIWHYSOFTWAREPROJECTSFAIL...CHAPTER1INTRODUCTION..........................3CHAPTER2WHYSOFTWAREISDIFFERENT................71.SoftwareIsComplex.......................82.SoftwareIsAbstract.......................103.RequirementsAreIncomplete.................114.TechnologyChangesRapidly..................125.BestPracticesAreNotMature.................136.TechnologyIsaVastDomain..................157.TechnologyExperienceIsIncomplete.............168.SoftwareDevelopmentIsResearch..............169.RepetitiveWorkIsAutomated.................1810.ConstructionIsActuallyDesign................1911.ChangeIsConsideredEasy..................2012.ChangeIsInevitable......................21Summary..............................22viii5505FM.qxd7/22/0511:49AMPageviiiCHAPTER3PROJECTMANAGEMENTASSUMPTIONS..........23HiddenAssumptions........................24ThePMBOK...........................24ScopeManagement........................25WhenShouldScopeDefinitionOccur?...........27TimeManagement.........................28ActivityDefinition........................28ActivitySequencing.......................30ActivityDurationEstimating..................34ScheduleDevelopment....................36CostManagement.........................37ResourcePlanning.......................38SoftwareDocumentation...................39DeveloperProductivity.....................42CostEstimating.........................43QualityManagement........................44Metrics..............................44Checklists............................45RiskManagement..........................45RiskAcceptance.................