Project Scope Management - PowerPoint Presentation

1. Project Scope Management (Day 2)Chapter 5

2. What is Project Scope Management?Scope refers to all the work involved in creating the products of the project and the processes used to create them2

3. Project Scope Management Processes3Process GroupIntegration Management ProcessMajor OutputPlanningP1: Plan Scope ManagementScope Mgmt PlanRequirement Mgmt PlanP2: Collect RequirementsReq. DocumentationReq. Traceability MatrixP3: Define ScopeProject Scope StmtProject Docs UpdateP4: Create WBSScope BaselineProject Docs UpdateMonitoring and ControllingMC1: Validate ScopeAccept DeliverablesChange RequestsWork Performance InfoMC2: Control ScopeChange RequestsProject Mgmt Plan UpdatesOrg, Process Asset Updates

4. Project Scope Management ProcessesPlanning scopeCollecting requirementsDefining scopeCreating the WBSValidating scopeControlling scope4

5. P3: Project Scope Statement - ExercisePOQ Organization – Online Shoe StoreReview the exercise and answer the questions at the bottom of the sheetWe will discuss each of these questions and then create the scope statement5

6. P4: Creating the Work Breakdown Structure (WBS)A WBS is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project6

7. P4: Sample Intranet WBS (Organized by Product )7

8. P4: Sample Intranet WBS(Organized by Phase)8

9. P4: Sample Intranet WBS(Organized by Phase)9Level 2Level 3Level 4

10. PMI Practice Standard for WBS 100 % Rule WBS should include 100% of the work defined by the project scope and capture ALL deliverables (internal, external, interim) in terms of work to be completed10

11. P4: Intranet WBS and Gantt Chart in MS Project11

12. P4: Intranet Gantt Chart Organized by Project Management Process Groups12

13. P4: Executing Tasks for JWD Consulting’s WBS13

14. Approaches to Developing a WBSUsing guidelines: Some organizations, like the DOD, provide guidelines for preparing WBSsanalogy approachtop-down approachbottom-up approachMind-mapping approach14

15. Figure 5-7. Sample Mind-Mapping Approach for Creating a WBS15

16. Figure 5-8. Gantt Charts With WBS Generated From a Mind Map16

17. The WBS Dictionary and Scope BaselineMany tasks are vague and must be explained more so people know what to do and can estimate how long it will take and what it will cost17WBS Dictionary

18. Advice for Creating a WBS and WBS DictionaryUnit of work should appear only once in WBS.Work content of WBS item is sum of items belowLimit responsibility of a WBS item to one individual (even though many people may be working on it)Project team member involvement in developing Document WBS items in WBS Dictionary18

19. Validating ScopeScope validation involves formal acceptance of the completed project deliverablesAcceptance is often achieved by a customer inspection and then sign-off on key deliverables19

20. Controlling ScopeScope control involves controlling changes to the project scope20

21. Controlling Scope21Goals of scope control influence the factors that cause scope changesassure changes are processed according to procedures developed as part of integrated change controlmanage changes when they occurVariance is the difference between planned and actual performance

22. Avoiding Scope Creep22Scope creep may occur as a result of:Poor change controlLack of proper initial identification and/or documentation of the features that are required for the achievement of project objectivesWeak project manager or executive sponsor

23. Scope Creep23To mitigate these types of issues, the proposed solutions are the following:Define requirements as “must-haves” and “nice to haves” Set project expectationsAgree on deliverables, and documentDocument and review business requirements

24. Best Practices - Avoiding Scope Problems1. Keep the scope realistic. Don’t make projects so large that they can’t be completed. 2. Involve users in project scope management. 3. Use off-the-shelf hardware and software whenever possible. 4. Follow good project management processes. 24

25. Scope Problems -> Project FailuresA project scope that is too broad and grandiose can cause severe problemsFoxMeyer DrugMcDonalds25

26. Improving User InputDevelop a good project selection process and insist that sponsors are from the user organizationHave users on the project team in important rolesHave regular meetings with defined agendas, and have users sign off on key deliverables presented at meetings26

27. Improving User InputDeliver something to users and sponsors on a regular basisDon’t promise to deliver when you know you can’tCo-locate users with developers27

28. Reduce Incomplete and Changing RequirementsRequirements management processUse techniques to get user involvementDocument and maintain requirementsCreate a requirements management databaseTesting throughout the project life cycleReview changes from a systems perspective28

29. Using Software to Assist in Project Scope ManagementWord-processing software helps create several scope-related documentsSpreadsheets help to perform financial calculations, weighed scoring models, and develop charts and graphsCommunication software like e-mail and the Web help clarify and communicate scope informationProject management software helps in creating a WBS, the basis for tasks on a Gantt chartSpecialized software is available to assist in project scope management29

30. Chapter SummaryProject scope managementMain processes include:Define scope managementCollect requirementsDefine scope (scope statement)Create WBSValidate scopeControl scope30