Master Project Management Plan.docx
《Master Project Management Plan.docx》由会员分享,可在线阅读,更多相关《Master Project Management Plan.docx(20页珍藏版)》请在冰豆网上搜索。
MasterProjectManagementPlan
MasterProjectManagementPlan
HealthandHumanServicesAgency,OfficeofSystemsIntegration
RevisionHistory
RevisionHistory
Revision/WorkSite#
DateofRelease
Owner
SummaryofChanges
InitialDraft2513v7
7/31/2004
SID-PMO
InitialRelease
OSIAdmin#5603
8/29/2008
OSI-PMO
Majorrevisionsmade.IncorporatedMasterProjectManagementPlantailoringguideinformationinthistemplate.
RemovetemplaterevisionhistoryandinsertMasterProjectManagementPlanrevisionhistory.
Approvals
,OSIProjectDirector
Date
,OSIProjectManager
Date
TemplateInstructions:
Thistemplateiscolorcodedtodifferentiatebetweenboilerplatelanguage,instructions,samplelanguage,andhyperlinks.Inconsiderationofthosereviewingablackandwhitehardcopyofthisdocumentwehavealsodifferentiatedthesesectionsofthedocumentusingvariousfontsandstyles.Detailsaredescribedbelow.Pleaseremovethetemplateinstructionswhenthedocumentisfinalized.
Standardboilerplatelanguagehasbeendevelopedforthismanagementplan.ThislanguageisidentifiedinblackArialfontandwillnotbemodifiedwithoutthepriorapprovaloftheOSIProjectManagementOffice(PMO).Iftheprojecthasidentifiedabusinessneedtomodifythestandardboilerplatelanguage,therequestmustbecommunicatedtothePMOforreview.
InstructionsforusingthistemplateareprovidedinblueTimesNewRomanfontanddescribegeneralinformationforcompletingthismanagementplan.Allbluetextshouldberemovedfromthefinalversionofthisplan.
SamplelanguageisidentifiedinreditalicArialfont.Thislanguageprovidessuggestionsforcompletingspecificsections.Allredtextshouldbereplacedwithproject-specificinformationandthefontcolorreplacedwithblacktext.
HyperlinksareannotatedinpurpleunderlinedArialtextandcanbeaccessedbyfollowingtheon-screeninstructions.Toreturntotheoriginaldocumentafteraccessingahyperlink,clickonthebackarrowinyourbrowser’stoolbar.The“FileDownload”dialogboxwillopen.Clickon“Open”toreturntothisdocument.
TableofContents
1.Introduction1
1.1Purpose1
1.2Scope1
1.3References1
1.3.1ProjectCentralizedDocumentRepository1
1.4Acronyms2
1.5DocumentMaintenance2
1.6MasterProjectPlan(MPP)vs.ProjectManagementPlan(PMP)2
2.ProjectPlanning3
2.1ScopeManagement3
2.1.1ScopeStatement3
2.1.2ScopeManagement3
2.1.3WorkBreakdownStructure4
2.1.4FormalAcceptanceofScope5
2.2TimeManagement5
2.3CostManagement6
2.4QualityManagement6
2.5StaffManagement6
2.6RiskManagement6
2.7CommunicationManagement7
2.8ConfigurationManagement7
2.9ContractManagement7
2.10GovernancePlanandIssueEscalationProcess7
2.11OrganizationalStructure8
2.12ProjectAssumptionsandConstraints8
2.12.1ProjectAssumptions8
2.13ProjectConstraints8
3.ProjectExecution9
3.1ProjectManagementPlanExecution9
3.2InformationDistribution9
3.3ApplicationCustomization9
4.ProjectControl10
4.1IntegratedChangeControl10
4.2ScopeChangeControl10
4.3ScheduleControl10
4.4PerformanceReporting11
5.UnanticipatedTasks12
6.ProjectSchedule12
7.PhaseClose-Out&LessonsLearned12
7.1.1ConductingFormalLessonsLearned12
7.1.2ContractCloseOut12
7.1.3AdministrativeClosure13
AppendixA-WorkBreakdownStructureA-1
AppendixB-ProjectScheduleB-1
1.
Introduction
1.1Purpose
ThepurposeoftheMasterProjectManagementPlanistocapture‘how’theprojectwillbemanagedthroughouttheprojectlifecycle.
ThepurposeoftheMasterProjectManagementPlan(MPP)documentistoprovidetheprojectstakeholderswithanapprovedworkingguideforhowtheProjectwillmanagetheproject.TheMPPdescribeshowtomanagetheactivitiesoftheProject,theprimecontractor,andothersupportingorganizationsthroughouttheprojectlifecyclephasestoensureatimely,efficient,andeffectivesystemacquisitionasdefinedintheProjectCharter.
1.2Scope
ThisMasterProjectManagementPlanidentifiestheactivities,processes,andproceduresusedtomanage.Definetheparametersthatthisplanencompasses.
TheMPPdescribestheoverallpurposeandscopeoftheMPPasadocument.ItprovideshowtheProjectofficewillbeorganized,staffed,anddescribeswhotheprojectstakeholdersare.TheMPPfurtherdetailsthemethodologyforprojectmanagementthatwillbeemployedforeachprojectlifecyclephase,aswellasabriefdescriptionofeachofthecomponentplansoftheMPP.
1.3References
ProjectManagementInstitute(PMI)
ProjectManagementBookofKnowledge(PMBOK3rdedition)
InstituteofElectrical&ElectronicsEngineers(IEEE)
SoftwareEngineeringInstitute(SEI)atCarnegie-MelonUniversity
StatewideInformationManagementManual(SIMM)
OSIBestPracticeswebsite(BPWeb)http:
//www.bestpractices.osi.ca.gov.
1.3.1ProjectCentralizedDocumentRepository
RefertotheWorkSiterepositorylocatedatforallproject-specificdocumentation.IftheprojectisnotusingWorkSite,indicatethelocationoftheproject’selectronicdocumentrepositoryaswellastheproject’shardcopylibrary.Iftheprojectisusingatooltotrackstaffinformationandthestaffingprofile,indicatethenameandlocationofthetool.
1.4Acronyms
BPWeb
BestPracticesWebsite
DGS
DepartmentofGeneralServices
DOF
DepartmentofFinance
DTS
DepartmentofTechnologyServices
IEEE
InstituteofElectrical&ElectronicsEngineers
MPP
MaterProjectPlan
OCIO
OfficeofChiefInformationOfficer
OSI
OfficeofSystemsIntegration
PMBOK
ProjectManagementBookofKnowledge
PMP
ProjectManagementPlan
SEI
SoftwareEngineeringInstitute(SEI)atCarnegie-MelonUniversity
SIMM
StatewideInformationManagementManual
WBS
WorkBreakdownStructure
1.5DocumentMaintenance
Thisdocumentwillbereviewedannuallyandupdatedasneeded,asaprojectproceedsthrougheachphaseofthesystemdevelopmentlifecycle.LessonslearnedasaresultofcontinuingstaffmanagementeffortswillbecapturedattheendofeachprojectphaseandusedtoimproveprojectandOSIstandards.Ifthedocumentiswritteninanolderformat,thedocumentshouldberevisedintothelatestOSItemplateformat.
Thisdocumentcontainsarevisionhistorylog.Whenchangesoccur,theversionnumberwillbeupdatedtothenextincrementandthedate,ownermakingthechange,andchangedescriptionwillberecordedintherevisionhistorylogofthedocument.
1.6MasterProjectManagementPlan(MPP)vs.ProjectManagementPlan(PMP)
TheMPPisdevelopedandcontrolledbytheprojectofficeandisthehighest-levelprojectmanagementdocument.TheMPPisfortheprojectofficetomanagetheentiresystemeffort.
ThePMPisacontractuallydefinedmanagementdocumentdevelopedbythecontractortomanagehisobligations.ThePMPissubordinatetotheMPPandmustbeintegratedviatheappropriatecontractingvehicles.
2.
ProjectPlanning
TheprojectmanagementplanisbasedprimarilyontheprojectmanagementprocessesdescribedinthePMBOK,3rdedition.ThemethodologyforplanningtheprojectutilizestheaspectsofthePMBOKwhereapplicabletotheprojectbasedonitssize,complexity,andstaffresources.
2.1ScopeManagement
2.1.1ScopeStatement
Thescopeoftheprojectistoprocureandimplementacentralized,integratedinformationmanagementsystemattoensurethatconditionsaremonitoredandtrackedaccordingtoprogramguidelinesthatmeettheintentoftheProject.
ThescopeoftheProjectisto:
∙Secureandretainprojectapprovalandfunding
∙Definebusinessrequirementsforthe
∙Upgradefacilitiestoimplement
∙EnsureVerificationandValidation,andIndependentProjectOversightareperformed
∙Procureavendortodesign,customize,testandimplementthe,andtheneededinterfacestoandfromexistingOSIsystems
∙Ensuretheprogramorganizationandstaffarepreparedfortheimplementation
∙Retiretheprevioussystem(s)softwareanddocumentationcomponents
∙CompletethePostImplementationandEvaluationReport
Thescopeoftheprojectdoesnotinclude:
∙Exploringnon-automatedsolutions,duetothecourtorder.
∙Installingthesystematlocationsotherthan.
∙Providingfunctionsoutsidethoserequired
.
2.1.2ScopeManagement
Theprojectscopewillbemanagedthroughthevariousmanagementplans,projectdocuments,reviews,andchangecontrolprocessesestablishedthroughouttheproject’sphases.Theprojectplanswillbedevelopedtoensurethattheprojectscopebaselineismaintainedandconsistent.ProjectdocumentswillbereviewedtoensurethescopeasestablishintheProjectCharter,FeasibilityStudyReport,andinthisProjectManagementPlanisnotinadvertentlyalteredorchanged.Theprojectscopewillprimarilybemanagedthroughtheproject’sscheduledreviewssuchasWeeklyStatusMeetings,Bi-WeeklyVendorMeetings,andmonthlySteeringCommitteeMeetings,andthroughthechangecontrolprocess.Communicationwillplayakeyroleinscopemanagement.TheprojecthasestablishseveralformsofverbalandwrittencommunicationdescribedintheCommunicationPlantoensurestakeholders,sponsors,executivemanagement,teammembers,externalagencies,andvendorsinvolvedintheprojecthaveaclearunder