ScopeManagementPlan文档格式.docx

ScopeManagementPlan文档格式.docx

《ScopeManagementPlan文档格式.docx》由会员分享，可在线阅读，更多相关《ScopeManagementPlan文档格式.docx（10页珍藏版）》请在冰点文库上搜索。

ManagementPlan

<

ProjectName>

CompanyName

StreetAddress

City,StateZipCode

Date

TableofContents

Introduction

ScopeManagementisthecollectionofprocesseswhichensurethattheprojectincludesalltheworkrequiredtocompleteitwhileexcludingallworkwhichisnotnecessarytocompleteit.TheScopeManagementPlandetailshowtheprojectscopewillbedefined,developed,andverified.Itclearlydefineswhoisresponsibleformanagingtheprojects’scopeandactsasaguideformanagingandcontrollingthescope.

ProjectScopeManagementfollowsafivestepprocess;

CollectRequirements,DefineScope,CreateWBS,VerifyScope,andControlScope.

1）CollectRequirements–thisfirststepistheprocessbywhichwedefineanddocumenttherequirementsneededtomeetallprojectobjectives.Thefoundationofthisprocessistheprojectcharterandstakeholderregister.Fromthese,theteamcanidentifyrequirements,collectivelydiscussdetailsassociatedwithmeetingeachrequirement,conductinterviewsandfollow-ondiscussiontoclarifytherequirements,anddocumenttherequirementsinsufficientdetailtomeasurethemoncetheprojectbeginstheexecutionphase.Thisdocumentationalsoservesasaninputtothenextstepintheprocesswhichistodefinescope.

2）DefineScope–thisstepiscriticaltoprojectsuccessasitrequiresthedevelopmentofadetailedproject/productdescriptiontoincludedeliverables,assumptions,andconstraintsandestablishestheframeworkwithinwhichprojectworkmustbeperformed.

3）CreateWBS–thisprocessbreaksprojectdeliverablesdownintoprogressivelysmallerandmoremanageablecomponentswhich,atthelowestlevel,arecalledworkpackages.Thishierarchicalstructureallowsformoresimplicityinscheduling,costing,monitoring,andcontrollingtheproject.

4）VerifyScope–thisistheprocessbywhichtheprojectteamreceivesaformalizedacceptanceofalldeliverableswiththesponsorand/orcustomer.

5）ControlScope–thisistheprocessofmonitoring/controllingtheproject/productscopeaswellasmanaginganychangesinthescopebaseline.Changesmaybenecessarytotheprojectscopebutitisimperativetheyarecontrolledandintegratedinordertopreventscopecreep.

TheScopeManagementPlanprovidesthescopeframeworkforthisproject.Thisplandocumentsthescopemanagementapproach;

rolesandresponsibilitiesastheypertaintoprojectscope;

scopedefinition;

verificationandcontrolmeasures;

scopechangecontrol;

andtheproject’sworkbreakdownstructure.Anyprojectcommunicationwhichpertainstotheproject’sscopeshouldadheretotheScopeManagementPlan.

Thisprojectisfordesigning,programming,andtestinganewsoftwareproductwhichwillbeusedtotrackthecompany’sfinancesandimprovevariousfinancialprocesses.Thisincludesdesignofthesoftware,allprogrammingandcoding,andtesting/validationofthesoftware.Noexternalresourcesoroutsourcingareanticipatedforthisproject.

ScopeManagementApproach

Itisimportantthattheapproachtomanagingtheprojects’scopebeclearlydefinedanddocumentedindetail.ThissectionprovidesasummaryoftheScopeManagementPlaninwhichitaddressesthefollowing:

Whohasauthorityandresponsibilityforscopemanagement

Howthescopeisdefined.ScopeStatement,WBS,WBSDictionary,StatementofWork,etc.）

Howthescopeismeasuredandverified.QualityChecklists,ScopeBaseline,WorkPerformanceMeasurements,etc.）

Thescopechangeprocess（whoinitiates,whoauthorizes,etc.）

Whoisresponsibleforacceptingthefinalprojectdeliverableandapprovesacceptanceofprojectscope

Forthisproject,scopemanagementwillbethesoleresponsibilityoftheProjectManager.ThescopeforthisprojectisdefinedbytheScopeStatement,WorkBreakdownStructure（WBS）andWBSDictionary.TheProjectManager,SponsorandStakeholderswillestablishandapprovedocumentationformeasuringprojectscopewhichincludesdeliverablequalitychecklistsandworkperformancemeasurements.ProposedscopechangesmaybeinitiatedbytheProjectManager,Stakeholdersoranymemberoftheprojectteam.AllchangerequestswillbesubmittedtotheProjectManagerwhowillthenevaluatetherequestedscopechange.UponacceptanceofthescopechangerequesttheProjectManagerwillsubmitthescopechangerequesttotheChangeControlBoardandProjectSponsorforacceptance.UponapprovalofscopechangesbytheChangeControlBoardandProjectSponsortheProjectManagerwillupdateallprojectdocumentsandcommunicatethescopechangetoallstakeholders.BasedonfeedbackandinputfromtheProjectManagerandStakeholders,theProjectSponsorisresponsiblefortheacceptanceofthefinalprojectdeliverablesandprojectscope.

RolesandResponsibilities

Inordertosuccessfullymanageaprojects’scopeit’simportantthatallrolesandresponsibilitiesforscopemanagementareclearlydefined.ThissectiondefinestheroleoftheProjectManager,ProjectTeam,Stakeholdersandotherkeypersonswhoareinvolvedinmanagingthescopeoftheproject.Itshouldstatewhoisresponsibleforscopemanagementandwhoisresponsibleforacceptingthedeliverablesoftheprojectasdefinedbytheprojects’scope.Anyotherrolesinscopemanagementshouldalsobestatedinthissection.

TheProjectManager,Sponsorandteamwillallplaykeyrolesinmanagingthescopeofthisproject.Assuch,theprojectsponsor,manager,andteammembersmustbeawareoftheirresponsibilitiesinordertoensurethatworkperformedontheprojectiswithintheestablishedscopethroughouttheentiredurationoftheproject.Thetablebelowdefinestherolesandresponsibilitiesforthescopemanagementofthisproject.

Name

Role

Responsibilities

JohnDoe

Sponsor

-Approveordenyscopechangerequestsasappropriate

-Evaluateneedforscopechangerequests

-Acceptprojectdeliverables

JaneDoe

ProjectManager

-Measureandverifyprojectscope

-Facilitatescopechangerequests

-Facilitateimpactassessmentsofscopechangerequests

-Organizeandfacilitatescheduledchangecontrolmeetings

-Communicateoutcomesofscopechangerequests

-Updateprojectdocumentsuponapprovalofallscopechanges

BobJones

TeamLead

-Validatescopechangerequests

-Participateinimpactassessmentsofscopechangerequests

-Communicateoutcomesofscopechangerequeststoteam

-Facilitateteamlevelchangereviewprocess

JohnSmith

TeamMember

-Participateindefiningchangeresolutions

-Evaluatetheneedforscopechangesandcommunicatethemtotheprojectmanagerasnecessary

TomBrown

Table,ScopeManagementRolesandResponsibilities

ScopeDefinition

Thescopedefinitionsectiondetailstheprocessofdevelopingadetaileddescriptionoftheprojectanditsdeliverables.Thiscanonlybecompletedaftertherequirementshavebeenidentifiedanddefinedduringtherequirementsdefinitionprocess.Duringtherequirementsdefinitionprocessthreedocumentswerecreated;

RequirementsDocumentation,RequirementsManagementPlanandaRequirementsTraceabilityMatrix.Youcanrefertothesedocumentswhendefiningtheprojects’scope.

Thissectionshouldexplaintheprocessyoufollowedtodevelopthedetaileddescriptionoftheprojectanditsdeliverables.IfyouusedotherdocumentssuchastheProjectCharter,PreliminaryProjectScopeStatementorRequirementsDocumentationyoushouldidentifythemandallotherdocumentsused.Youshouldtiethescopedefinitionprocessbacktotherequirementsdefinitionastheprojects’scopeanswerstherequirementsfortheproject.

Youshouldalsodocumentthetoolsandtechniquesusedtodefinetheprojectscopesuchasexpertjudgment,productanalysis,alternativesidentificationorfacilitatedworkshops.

Thescopeforthisprojectwasdefinedthroughacomprehensiverequirementscollectionprocess.First,athoroughanalysiswasperformedonthecompany’scurrentsoftwareapplicationsbasedonemployeeanduserfeedback.Fromthisinformation,theprojectteamdevelopedtheprojectrequirementsdocumentation,therequirementsmanagementplan,andtherequirementstraceabilitymatrixforwhatthenewsoftwareapplicationmustaccomplish.

Theprojectdescriptionanddeliverablesweredevelopedbasedontherequirementscollectionprocessandinputfromsubjectmatterexpertsinsoftwaredesign,technicalsupport,programmingandbusinessapplications.Thisprocessofexpertjudgmentprovidedfeedbackonthemosteffectivewaystomeettheoriginalrequirementsofprovidinganewsoftwareplatformfromwhichthecompanycanimproveitsfinancialtrackingandinternalfinancialprocesses.

ProjectScopeStatement

Theprojectscopestatementdetailstheproject’sdeliverablesandtheworknecessarytocreatethesedeliverables.TheProjectScopeStatementshouldcontainthefollowingcomponents:

ProductScopeDescription–describeswhattheprojectwillaccomplish

ProductAcceptanceCriteria–describeswhatrequirementsmustbemetinorderfortheprojecttobeacceptedascomplete

ProjectDeliverables–detailedlistofdeliverablestheprojectwillresultin

ProjectExclusions–descriptionofworkth