1. Project Scope ManagementWaleed El-Naggar, MBA, PMP

2. Agenda Introduction to Project Scope Collect Requirements Define Scope Create WBS Control Scope Verify Scope 10/06/2009Prepared by: Waleed El-Naggar 2 3. What is Project Scope? Scope refers to all the work involved in creatingthe products of the project and the processesused to create them. Project scope management includes theprocesses required to ensure that the projectincludes all the work required, and only the workrequired, to complete the project successfully. 10/06/2009 Prepared by: Waleed El-Naggar 3 4. Product Scope vs. Project Scope Product scope: The futures & functions thatcharacterize the product, service, or result. Project Scope: The work that needs to beaccomplished to deliver a product, service, orresult with the specified features andfunctions. 10/06/2009Prepared by: Waleed El-Naggar 4 5. ProjectScopeManagementProcesses 10/06/2009 Prepared by: Waleed El-Naggar 5 6. 5.1 Collect requirements The process of defining and documentingstakeholders needs to meet the projectobjectives. Requirements includes the quantified anddocumented needs and expectations of thesponsor, customer, and other stakeholders. Requirement must be analyzed and recordedin a clear and detailed way to be measured. 10/06/2009 Prepared by: Waleed El-Naggar 6 7. Collect Requirements Data Flow10/06/2009 Prepared by: Waleed El-Naggar 7 8. Collect Requirements: Inputs1. Project Charter: a document issues by the project initiator or sponsor that formally authorizes the existence of the project, and provides the project manager with authority to apply organizational resources to project activities. (Output of process 4.1)2. Stakeholder Register: a document used to identify stakeholders with a particular interest in, or impact on, the project. 10/06/2009Prepared by: Waleed El-Naggar 8 9. SampleProjectCharter10/06/2009 Prepared by: Waleed El-Naggar 9 10. Collect Requirements: T & T (1)1. Interviews: meeting the stakeholders to ask prepared and spontaneous question & recording the responses.2. Focus groups: bring together stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service or result. 10/06/2009Prepared by: Waleed El-Naggar 10 11. Collect Requirements: T & T (2)3. Facilitated Workshops: Focused session with key cross-functional stakeholders to define product requirements.4. Group Creativity Techniques: Brainstorming Nominal Group Delphi Technique Idea/Mind Mapping Affinity Diagram 10/06/2009 Prepared by: Waleed El-Naggar 11 12. Collect Requirements: T & T (3)5. Group Decision Making Techniques Unanimity Majority Plurality Dictatorship6. Questionnaire and Surveys7. Observations8. Prototypes 10/06/2009Prepared by: Waleed El-Naggar 12 13. Collect Requirements: Outputs1. Requirements Document2. Requirements Management Plan3. Requirements Traceability 10/06/2009 Prepared by: Waleed El-Naggar 13 14. QuizThe best tool in collecting requirements for across-functional project is:A. Facilitated WorkshopsB. InterviewsC. SurveysD. Brainstorming The answer is: A 10/06/2009 Prepared by: Waleed El-Naggar 14 15. 5.2 Define ScopeThe process of developing a detailed descriptionof the project and product. 10/06/2009Prepared by: Waleed El-Naggar 15 16. DefineScopeDataFlow10/06/2009 Prepared by: Waleed El-Naggar 16 17. Define Scope: Inputs1. Project charter2. Requirements Document3. Organizational Process Assets Procedures & Templates Lessons learned from old Projects 10/06/2009Prepared by: Waleed El-Naggar 17 18. Define Scope: T & T1. Expert Judgment2. Product Analysis3. Alternatives Identification4. Facilitated workshops 10/06/2009 Prepared by: Waleed El-Naggar 18 19. Define Scope: Outputs (1)1. Scope Statement: describes projects deliverables and the work required to create those deliverables. It includes Product scope description Product acceptance criteria Project Deliverables Project Exclusion Project Assumptions 10/06/2009 Prepared by: Waleed El-Naggar 19 20. Define Scope: Outputs (2)2. Project Documents Updates: may include,but not limited to: Stakeholder register Requirements Documents Requirements Traceability Matrix 10/06/2009Prepared by: Waleed El-Naggar 20 21. QuizWhy would you consider the scope statement so importantin your project management methodology?A. Mandatory to consult the plan before accepting change.B. Project managers must document any changes before approving or declining them.C. The project scope serves as a reference for all future project decisions.D. The project plan and EVM work together to assess the risk involved with proposed changes The answer is: C10/06/2009Prepared by: Waleed El-Naggar 21 22. 5.3 Create WBS Subdividing the project deliverables and project work into smaller and more manageable components. The work breakdown structure is a deliverable-oriented hierarchical decomposition of project work. 10/06/2009Prepared by: Waleed El-Naggar 22 23. Create WBS: Data Flow10/06/2009Prepared by: Waleed El-Naggar 23 24. Sample WBS (1)10/06/2009 Prepared by: Waleed El-Naggar 24 25. Sample WBS (2)10/06/2009 Prepared by: Waleed El-Naggar 25 26. Create WBS: Inputs1. Project Scope Statement2. Requirements Document3. Organizational Process Assets 10/06/2009Prepared by: Waleed El-Naggar 26 27. Create WBS: T & T1. DecompositionThe subdivision of project deliverables intosmaller, more manageable components. Thework package level is the lowest level in theWBS, and is the point at which the cost anactivity durations can be reliably estimated andmanaged. The level of detail for work packageswill vary with the size and complexity of theproject. 10/06/2009 Prepared by: Waleed El-Naggar 27 28. Create WBS: Outputs1. WBS2. WBS Dictionary A number Identifier Who is responsible for what A description of each work package Any related codes 10/06/2009Prepared by: Waleed El-Naggar 28 29. Create WBS: Outputs3. Scope baseline4. Project Documents updates 10/06/2009Prepared by: Waleed El-Naggar 29 30. QuizA work breakdown structure numbering system allowsproject staff to:A. Systematically estimate costs of work breakdown structure elements.B. Provide project justificationC. Identify the level at which individual elements are foundD. Use it in project management software The answer is: C10/06/2009 Prepared by: Waleed El-Naggar 30 31. QuizWhich of the following documents contain detaileddescriptions of work packages?A. Work breakdown structure (WBS) dictionaryB. Activity listC. Preliminary project scope statementD. Project scope management planThe answer is: A10/06/2009 Prepared by: Waleed El-Naggar 31 32. QuizThe work breakdown structure can best be thought of as aneffective aid for ___________ communicationA. TeamB. Project managerC. CustomerD. stakeholders The answer is: D 10/06/2009Prepared by: Waleed El-Naggar 32 33. 5.4 Verify Scope Formalizing acceptance of the completed project deliverables. Includes reviewing deliverables with the client and obtaining formal acceptance of deliverables. Scope verification is concerned with acceptanceof deliverables while quality control is concerned with correctness of the deliverables and meeting quality requirements. 10/06/2009Prepared by: Waleed El-Naggar 33 34. Verify Scope: Data Flow Diagram10/06/2009Prepared by: Waleed El-Naggar 34 35. Verify Scope: Inputs1. Project Management Plan Scope statement WBS WBS Dictionary.2. Requirements Documentation3. Requirements Traceability Matrix4. Validated Deliverables 10/06/2009Prepared by: Waleed El-Naggar 35 36. Verify Scope: T & T1. Inspection: measuring, and verifying to determine whether work and deliverables meet requirements and product acceptance criteria. Inspections are sometimes called reviews, audits, and walkthroughs. 10/06/2009Prepared by: Waleed El-Naggar 36 37. Verify Scope: Outputs1. Accepted Deliverables2. Change Requests3. Project Document Updates 10/06/2009Prepared by: Waleed El-Naggar 37 38. QuizWhich of the following is an output of scopeverification?A. WBS templateB. ReworkC. Formal acceptanceD. SOW acceptanceThe answer is: C 10/06/2009 Prepared by: Waleed El-Naggar 38 39. 5.5 Control Scope Monitoring the status of the project andproducts scope Managing changes to scope baseline Ensure all requested changes andrecommended corrective or preventive actionsare processed through the Perform IntegratedChange Control process (4.5) Uncontrolled changes are often referred to asproject scope creep. 10/06/2009Prepared by: Waleed El-Naggar 39 40. Control Scope: Inputs (1)1. Project Management Plan Scope baseline Scope management plan Change management plan Configuration management plan Requirements management plan2. Work Performance Indicators 10/06/2009Prepared by: Waleed El-Naggar 40 41. Control Scope: Inputs (2)3. Requirements Documentation4. Requirements Traceability Matrix5. Organizational Process Assets 10/06/2009 Prepared by: Waleed El-Naggar 41 42. Control Scope: T & T1. Variance Analysis Analyze performance measurements to assess the variation from the baseline scope. Analysis should determine the cause and degree of variance. 10/06/2009Prepared by: Waleed El-Naggar 42 43. Control Scope: Outputs1. Work Performance Measurement2. Organizational Process Asset Updates3. Change Requests4. Project Management Plan Updates5. Project Document Updates 10/06/2009 Prepared by: Waleed El-Naggar 43 44. QuizDuring a project team meeting, a team member suggestsan enhancement to the scope that is beyond the scope ofthe project charter. The project manager points out thatthe team needs to concentrate on completing all the workand only the work required. This is an example of:A. Change management process.B. scope management.C. quality analysis.D. scope decomposition. The answer is: B10/06/2009Prepared by: Waleed El-Naggar 44 45. QuizWhich of the following is the KEY attribute of scopeverification?A. More complete project scope management planB. Customer acceptance of project deliverablesC. Improved schedule estimatesD. An improved project management information system.The answer is: B 10/06/2009 Prepared by: Waleed El-Naggar 45 46. Thank you waleed_k@aucegypt.edu10/06/2009Prepared by: Waleed El-Naggar 46