Table Of Content

Practical Software Process Improvement DISCLAIMEROFWARRANTY Thetechnicaldescriptions,procedures,andcomputerprogramsinthisbookhave beendevelopedwiththegreatestofcareandtheyhavebeenusefultotheauthor inabroadrangeofapplications;however,theyareprovidedasis,withoutwar- rantyofanykind.ArtechHouse,Inc.,andtheauthorandeditorsofthebooktitled PracticalSoftwareProcessImprovementmakenowarranties,expressedorimplied, thattheequations,programs,andproceduresinthisbookoritsassociatedsoft- warearefreeoferror,orareconsistentwithanyparticularstandardofmerchant- ability,orwillmeetyourrequirementsforanyparticularapplication.Theyshould notberelieduponforsolvingaproblemwhoseincorrectsolutioncouldresultin injurytoapersonorlossofproperty.Anyuseoftheprogramsorproceduresin suchamannerisattheuser’sownrisk.Theeditors,author,andpublisherdisclaim allliabilityfordirect,incidental,orconsequentdamagesresultingfromuseofthe programsorproceduresinthisbookortheassociatedsoftware. ForalistingofrecenttitlesintheArtechHouseComputerLibrary, turntothebackofthisbook. Practical Software Process Improvement Robert Fantina artechhouse.com LibraryofCongressCataloging-in-PublicationData AcatalogrecordforthisbookisavailablefromtheU.S.LibraryofCongress. BritishLibraryCataloguinginPublicationData Fantina,Robert Practicalsoftwareprocessimprovement.—(ArtechHousecomputinglibrary) 1.Computersoftware—Development—Management I.Title 005.1’068 ISBN1-58053-959-9 CoverdesignbyIgorValdman ©2005ARTECHHOUSE,INC. 685CantonStreet Norwood,MA02062 InternationalStandardBookNumber: 1-58053-959-9 10987654321 ToEdwinaandTravis . Contents 1 Introduction. . . . . . . . . . . . . . . . . . . . . . . 1 1.1 Beginning . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 FormatandUseofthisBook . . . . . . . . . . . . . . . . 4 1.3 TheAssessment . . . . . . . . . . . . . . . . . . . . . . 8 Reference 11 2 Software Requirements Management/Requirements Management. . . . . . . . . . . . . . . . . . . . . . 13 2.1 GapAnalysisforRequirementsManagement . . . . . . . . . 14 2.1.1 ResponsibilityforRequirementsIsAssigned . . . . . . . . 17 2.1.2 RequirementsAreCreatedonaStandardTemplatefor EaseofDocumentation. . . . . . . . . . . . . . . . . 18 2.1.3 TheRequirementsDocumentIsBaselined . . . . . . . . . 19 2.1.4 ChangestotheRequirementsDocumentAreReviewedand IncorporatedintotheSoftwareProject. . . . . . . . . . . 19 2.2 RequirementsManagementFlowchart . . . . . . . . . . . . 22 vii viii PracticalSoftwareProcessImprovement 2.3 SoftwareRequirementsManagement/Requirements ManagementChecklist . . . . . . . . . . . . . . . . . . 22 SelectedBibliography 24 References 25 3 Software Project Planning/Project Planning. . . . . . 27 3.1 GapAnalysisforSoftwareProjectPlanning/ProjectPlanning . . 29 3.1.1 ADocumentedProcedureforAssigningProjectPlanning ResponsibilityIsEstablished. . . . . . . . . . . . . . . 32 3.1.2 AStandard,TailorableFormatforAllProjectPlansIs EstablishedandDocumented . . . . . . . . . . . . . . 33 3.1.3 ScheduleEstimatesAreMadeasPartofProjectPlanning, AccordingtoaDocumentedProcedure . . . . . . . . . . 36 3.1.4 CostEstimatesAreMadeasPartofProjectPlanning, AccordingtoaDocumentedProcedure . . . . . . . . . . 38 3.1.5 TheProjectPlanIsBaselinedAccordingtoaDocumented Procedure . . . . . . . . . . . . . . . . . . . . . . 39 3.1.6 ChangeRequestsMustUndergoImpactAnalysisandApproval ofanyBudgetorScheduleAdjustments,Accordingtoa DocumentedProcedure. . . . . . . . . . . . . . . . . 40 3.2 SoftwareProjectPlanning/ProjectPlanningFlowchart . . . . . 43 3.3 SoftwareProjectPlanning/ProjectPlanningChecklist . . . . . 44 SelectedBibliography 46 References 46 4 Software Project Tracking and Oversight/Project Monitoring and Control . . . . . . . . . . . . . . . . 47 4.1 GapAnalysisforProjectTrackingandOversight/Project MonitoringandControl. . . . . . . . . . . . . . . . . . 48 4.1.1 TheProjectPlanIsUsedforTracking . . . . . . . . . . . 52 4.1.2 FormalReviewsAreHeld. . . . . . . . . . . . . . . . 53 4.1.3 BudgetActualsAreTracked. . . . . . . . . . . . . . . 54 4.1.4 ScheduleActualsAreTracked . . . . . . . . . . . . . . 56 4.1.5 IdentifiedRisksAreTracked. . . . . . . . . . . . . . . 57 4.1.6 ChangestotheProjectPlanAreMadeAccordingtoa DocumentedProcedure. . . . . . . . . . . . . . . . . 58 Contents ix 4.2 ProjectTrackingandOversight/Planning,Monitoring,and ControlFlowchart . . . . . . . . . . . . . . . . . . . . 61 4.3 SoftwareProjectTrackingandOversight/ProjectMonitoring andControlChecklist . . . . . . . . . . . . . . . . . . . 61 References 63 5 Software Subcontract Management/Supplier Agreement Management . . . . . . . . . . . . . . . 65 5.1 GapAnalysisforSoftwareSubcontractorManagement/Supplier AgreementManagement;Part1:SubcontractorSelection. . . . 68 5.2 SoftwareSubcontractorManagement/SupplierAgreement Management;Part1:SelectingtheSubcontractor . . . . . . . 71 5.2.1 ProjectOutsourcingDecisionsAreMadeAccordingtoa DocumentedProcedure. . . . . . . . . . . . . . . . . 72 5.2.2 CandidateVendorsAreSelectedBasedonaDocumented Procedure . . . . . . . . . . . . . . . . . . . . . . 72 5.2.3 ProposalsAreReceivedfromAllSubcontractorsUnder Consideration . . . . . . . . . . . . . . . . . . . . 73 5.2.4 TheSubcontractorsUnderConsiderationHavetheResources— PersonnelandFacilities—toPerformtheWork . . . . . . . 74 5.2.5 EithertheWorktobePerformedorManagementIsLocated SufficientlyConvenienttothePrimeContractorforFace-to- FaceMeetingsAsMayBeNecessary . . . . . . . . . . . 75 5.2.6 TheSubcontractorProvidesAdequateReferencesfromSatisfied Customers . . . . . . . . . . . . . . . . . . . . . . 75 5.3 SoftwareSubcontractorManagement/SupplierAgreement Management;Part2:MonitoringtheWorkoftheSubcontractor. 75 5.4 GapAnalysisforSoftwareSubcontractorManagement/Supplier AgreementManagement;Part2:SubcontractorManagement . . 76 5.4.1 TheSubcontractorWorksfromaProjectPlanThatIs SubmittedtothePrimeContractor . . . . . . . . . . . . 79 5.4.2 ThePrimeContractor’sProjectManagerMonitorsthe Subcontractor’sProjectPlantoAssureThattheProjectIs BeingPerformedasAgreed . . . . . . . . . . . . . . . 80 5.4.3 ThePrimeContractor’sProjectManagerFacilitatesPeriodic TechnicalReviewswiththeSubcontractor . . . . . . . . . 81