Project Scope Management
Project Scope ManagementThe processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully
Answers the question What will the project produce in the end.
Why Do We Manage Scope?Cant manage schedule and budget if scope is out of control (Triple Constraint)Scope docs are used to manage expectationsTIMECOSTSCOPEQuality
Scope Management Key PointsWhat is scope managementChecking to ensure that one is completing workSaying No to additional work not in the charterPreventing extra work/gold platingWork Breakdown Structure (WBS)Foundation of the project, all planning and controlling is based on the WBS Identifies all work to be performed, if it is not in the WBS it does not need to be doneGraphical picture of workWBSEstimatingNetwork DiagramsStaffingRisk
How Do We Manage Scope?Five processesCollect RequirementsDefine ScopeCreate WBSVerify ScopeControl Scope
Collect RequirementsProject CharterInterviewsFocus groupsFacilitated workshopsGroup creativity techniquesGroup decision making techniquesQuestionnaires and surveysObservationsPrototypes
InputsOutputsTools & TechniquesRequirements docsStakeholder RegisterRequirements mgmt planRequirements traceability matrix
Collect RequirementsDetermine product of the project requirementsMake sure all requirements support the business need of the project as described in the charter
Define ScopeOrganizational Process AssetsProject CharterExpert judgement Product analysisAlternatives identificationFacilitated workshops
InputsTools & TechniquesProject Document UpdatesOutputsProject Scope StatementRequirements documentation
Project Scope StatementProduct scope descriptionProduct acceptance criteriaProject deliverablesProject exclusionsProject constraintsProject assumptions
Remember the difference between product and project?
Create WBSProject scope statementRequirements documentationOrganizational process assetsDecompositionInputsTools & TechniquesWork Breakdown Structure (WBS)WBS DictionaryOutputsScope BaselineProject Document Updates
Work Breakdown StructureStart with major project deliverables or phasesDecomposition is breaking down the deliverables into more manageable partsNot all branches need the same level of decomposition!Decompose into Work Packages8-80 Hour Rule Dont break work down too much
Work Breakdown Structure
Verify ScopeProject Management PlanRequirements DocumentationRequirements Traceability MatrixInspectionInputsTools & TechniquesAccepted DeliverablesValidated DeliverablesChange RequestsOutputsProject Document Updates
Control ScopeProject Management PlanWork Performance InformationRequirements DocumentationVariance analysisInputsTools & TechniquesRequirements Traceability MatrixWork Performance MeasuresOutputsOrganizational Process AssetsOrganizational Process AssetsChange RequestsProject Management Plan UpdatesProject Document Updates
Scope DefinitionsChange Control SystemDocumentation, tracking, and approvals required to change project scopeConfiguration Management System Documentation, tracking, and approvals required to change product scopeManagement by Objectives (MBO)Establish unambiguous and realistic objectivesPeriodically evaluate if objectives are being metTake corrective action
Other Topics Project SelectionBenefit Measurement Methods (Comparative Approach)Murder Board Panel that tries to shoot down new ideasScoring ModelsBenefit Compared to CostConstrained Optimization Methods (Mathematical)Linear ProgrammingInteger ProgrammingMulti-Objective Programming
****************
Top Related