ExampleIEEEsoftwareprojectmanagementplan(SPMP)Source:Object‐

Oriented&ClassicalSoftwareEngineering,7thedition,StephenR.Schach,pg.590‐
594ThisplanisfordevelopmentoftheMSGproductbyasmallsoftwareorganizationconsistingofthreeindivi
duals:Al,theownerofthecompany,andtwosoftwareengineers,BettyandCharlie.TheMSGproductistodev
elopasoftwareproducttosupporttheMarthaStocktonGreengage(MSG)Foundationthathelpsyoungcou
plesinpurchasingtheirownhomesbyprovidinglow‐
costloans.Thesoftwaremustdeterminehowmuchmoneyisavailableeachweektofundloans.Todothis,the
systemmustalsohelpintheapplicationandtrackingofmortgages,managefoundationinvestments,andest
imateincomingandoutgoingcashflow.1Overview1.1ProjectSummary1.1.1Purpose,scope,andobjective
s.TheobjectofthisprojectistodevelopasoftwareproductthatwillassisttheMarthaStocktonGreengage(M
SG)Foundationinmakingdecisionsregardinghomemortgagesformarriedcouples.Theproductwillallowth
eclienttoadd,modify,anddeleteinformationregardingtheFoundation’sinvestments,operatingexpenses
,andindividualmortgageinformation.Theproductwillperformtherequiredcalculationsintheseareasand
producereportslistinginvestments,mortgages,andweeklyoperationexpenses.1.1.2Assumptionsandco
nstraints.Constraintsincludethefollowing:•Thedeadlinemustbemet.•Thebudgetconstraintmustbemet
.•Theproductmustbereliable.•Thearchitecturemustbeopensothatadditionalfunctionalitymaybeadde
dlater.•Theproductmustbeuser‐
friendly.1.1.3Projectdeliverables.Thecompleteproduct,includingusermanual,willbedelivered10weeks
aftertheprojectcommences.1.1.4Scheduleandbudgetsummary.Theduration,personnelrequirements,
andbudgetofeachworkflowareasfollows:•Requirementsworkflow(1week,twoteammembers,$3740)•
Analysisworkflow(2weeks,twoteammembers,$7480)•Designworkflow(2weeks,twoteammembers,$7
480)•Implementationworkflow(3weeks,threeteammembers,$16,830)•Testingworkflow(2weeks,thre
eteammembers,$11,220)

Thetotaldevelopmenttimeis10weeks,andthetotalinternalcostis$46,750.1.2Evolutionoftheprojectman
agementplan.AllchangestotheprojectmanagementplanmustbeagreedtobyAlbeforetheyareimplemen
ted.Allchangesshouldbedocumentedinordertokeeptheprojectmanagementplancorrectanduptodate.
2Referencematerials.Allartifactswillconformtothecompany’sprogramming,documentation,andtestin
gstandards.3Definitionsandacronyms.MSG‐
MarthaStocktonGreengage;theMSGFoundationisourclient.4Projectorganization4.1Externalinterfaces
.AlltheworkonthisprojectwillbeperformedbyAl,Betty,andCharlie.Alwillmeetweeklywiththeclienttorep
ortprogressanddiscusspossiblechangesandmodifications.4.2Internalstructure.Thedevelopmentteamc
onsistsofAl(owner),Betty,andCharlie.4.3Rolesandresponsibilities.BettyandCharliewillperformthedesi
gnworkflow.Alwillimplementtheclassdefinitionsandreportartifacts,Bettywillconstructtheartifactstoha
ndleinvestmentsandoperatingexpenses,andCharliewilldeveloptheartifactsthathandlemortgages.Each
memberisresponsibleforthequalityoftheartifactsheorsheproduces.Alwilloverseeintegrationandtheov
erallqualityofthesoftwareproductandwillliaisewiththeclient.5Managerialprocessplans5.1Start‐
upplan5.1.1Estimationplan.Aspreviouslystated,thetotaldevelopmenttimeisestimatedtobe10weeksan
dthetotalinternalcosttobe$46,750.Thesefigureswereobtainedbyexpertjudgmentbyanalogy,thatis,byc
omparisonwithsimilarprojects.5.1.2Staffingplan.Alisneededfortheentire10weeks,forthefirst5weeksin
onlyamanagerialcapacityandthesecond5weeksasbothmanagerandprogrammer.BettyandCharliearen
eededfortheentire10weeks,forthefirst5weeksassystemsanalysisanddesignersandforthesecond5week
sasprogrammersandtesters.5.1.3Resourceacquisitionplan.Allnecessaryhardware,software,andCASEt
oolsfortheprojectarealreadyavailable.TheproductwillbedeliveredtoMSGFoundationinstalledonadeskt
opcomputerthatwillbeleasedfromourusualsupplier.5.1.4Projectstafftrainingplan.Noadditionalstafftra
iningisneededforthisproject.5.2Workplan5.2.1WorkactivitiesandScheduleallocationWeek1(Complete
d)Metwithclient,anddeterminedrequirementsartifacts.Inspectedrequirementsartifacts.Weeks2,3(Co
mpleted)Producedanalysisartifacts,andinspectedanalysisartifacts.Showedartifactstoclient,whoappro
vedthem.Producedsoftwareprojectmanagement

plan,andinspectedsoftwareprojectmanagementplan.Weeks4,5Productdesignartifacts,andinspectdesi
gnartifactsWeeks6‐
10Implementationandinspectionofeachclass,unittestinganddocumentation,integrationofeachclass,in
tegrationtesting,producttesting,anddocumentationinspection.5.2.2Resourceallocation.Thethreetea
mmemberswillworkseparatelyontheirassignedartifacts.Al’sassignedrolewillbetomonitorthedailyprog
ressoftheothertwo,overseeimplementation,beresponsibleforoverallquality,andinteractwiththeclient.
Teammemberswillmeetattheendofeachdayanddiscussproblemsandprogress.Formalmeetingswiththe
clientwillbeheldattheendofeachweektoreportprogressanddetermineifanychangesneedtobemade.AL
willensurethatscheduleandbudgetrequirementsaremet.RiskmanagementwillalsobeAl’sresponsibility.
Minimizingfaultsandmaximizinguser‐
friendlinesswillbeAl’stoppriorities.Alhasoverallresponsibilityforalldocumentationandhastoensurethat
itisuptodate.5.2.3Budgetallocation.Thebudgetforeachworkflowisasfollows:Requirementsworkflow$3
,740Analysisworkflow$7,480Designworkflow$7,480Implementationworkflow$16,830Testingworkflo
w$11,220Total$46,7505.3ControlplanAnymajorchangesthataffectthemilestonesorthebudgethavetob
eapprovedbyAlanddocumented.Nooutsidequalityassurancepersonnelareinvolved.Thebenefitsofhavi
ngsomeoneotherthantheindividualwhocarriedoutthedevelopmentdothetestingwillbeaccomplishedb
yeachpersontestinganotherperson’sworkproducts.Alwillberesponsibleforensuringthattheprojectisco
mpletedontimeandwithinbudget.Thiswillbeaccomplishedthroughdailymeetingswiththeteammember
s.Ateachmeeting,BettyandCharliewillpresenttheday’sprogressandproblems.Alwilldeterminewhethert
heyareprogressingasexpectedandwhethertheyarefollowingthespecificationdocumentandtheproject
managementplan.AnymajorproblemsfacedbytheteammemberswillimmediatelybereportedtoAl.

5.4RiskmanagementplanTheriskfactorsandthetrackingmechanismsareasfollows.Thereisnoexistingpro
ductwithwhichthenewproductcanbecompared.Accordingly,itwillnotbepossibletoruntheproductinpar
allelwithanexistingone.Therefore,theproductshouldbesubjectedtoextensivetesting.Theclientisassum
edtobeinexperiencedwithcomputers.Therefore,specialattentionshouldbepaidtotheanalysisworkflow
andcommunicationwiththeclient.Theproducthastobemadeasuser‐
friendlyaspossible.Becauseoftheever‐
presentpossibilityofamajordesignfault,extensivetestingwillbeperformedduringthedesignworkflow.Als
o,eachoftheteammemberswillinitiallytesthisorherowncodeandthentestthecodeofanothermember.Al
willberesponsibleforintegrationtestingandinchargeofproducttesting.Theinformationmustmeetthespe
cifiedstoragerequirementsandresponsetimes.Thisshouldnotbeamajorproblembecauseofthesmallsize
oftheproduct,butitwillbemonitoredbyAlthroughoutdevelopment.Thereisaslimchanceofhardwarefailu
re,inwhichcaseanothermachinewillbeleased.Ifthereisafaultinthecompiler,itwillbereplaced.Thesearec
overedinthewarrantiesreceivedfromthehardwareandcompilerssuppliers5.5Projectclose‐
outplan.Notapplicablehere.6Technicalprocessplans6.1Processmodel.TheUnifiedProcesswillbeused.6.
2Methods,tools,andtechniques.TheworkflowswillbeperformedinaccordancewiththeUnifiedProcess.T
heproductwillbeimplementedinJava.6.3Infrastructureplan.TheproductwillbedevelopedusingArgoUM
LrunningunderLinuxonapersonalcomputer.6.4Productacceptanceplan.Acceptanceoftheproductbyour
clientwillbeachievedbyfollowingthestepsoftheUnifiedProcess.7Supportingprocessplans7.1Configurat
ionmanagementplan.CVSwillbeusedthroughoutforallartifacts.7.2Testingplan–
ThetestingworkflowoftheUnifiedProcesswillbeperformed.7.3Documentationplan–
DocumentationwillbeproducedasspecifiedintheUnifiedProcess.7.4Qualityassuranceplanand7.5Revie
wsandauditsplan.BettyandCharliewilltesteachother’scode,andAlwillconductintegrationtesting.Extens
iveproducttestingwillthenbeperformedbyallthree.