Chapter p 5 Project Scope Management (PMBOK Guide) Mohammad h d A. Rajabi j bi Dept. of Geomatics Eng., University of Tehran Tel: +98 21 8833 4341, Cell: +98 912 132 5823 Email: marajabi@ut.ac.ir Homepage: http://www.marajabi.com Table of Content Guide to PMBOK © Mohammad A. Rajabi 2 Introduction • Processes to ensure that h allll workk required, i d and d only the work required for completing the project successfully f ll • What is included/what is not included • Collect requirement • Define scope • Create WBS • Verify scope • Control scope Guide to PMBOK © Mohammad A. Rajabi 3 Guide to PMBOK © Mohammad A. Rajabi 4 5 1 Collect Requirement 5.1 • Defining and documenting stakeholders • Analyzing their requirements Guide to PMBOK © Mohammad A. Rajabi 5 Inputs, Tools & Techniques, Outputs Guide to PMBOK © Mohammad A. Rajabi 6 Data Flow Guide to PMBOK © Mohammad A. Rajabi 7 Inputs • Project charter – High‐level g requirements q – High‐level product description • Stakeholder St k h ld register it Guide to PMBOK © Mohammad A. Rajabi 8 Tools & Techniques • Interviews – Formal/informal, / , one‐on‐one • Focus groups – Pre‐qualified P lifi d stakeholders k h ld & subject bj matter experts • Facilitated workshop – Cross Cross‐functional functional stakeholders • Group creativity techniques • Guide to PMBOK © Mohammad A. Rajabi 9 Tools & Techniques – Brainstorming – Nominal group technique (voting for the rank ideas) – The Delphi techniques (experts answer questionnaires) – Idea/mind / mapping pp g ((commonality/differences) y/ ) – Affinity diagram (ideas sorted into groups) • Group decision making techniques – – – – Unanimity Majority Plurality Dictatorship Guide to PMBOK © Mohammad A. Rajabi 10 Tools & Techniques • Questionnaires and surveys • Observations • Prototypes Guide to PMBOK © Mohammad A. Rajabi 11 Outputs • Requirement documentation – Unambiguous (measurable & testable), Traceable, Consistent, Acceptable to key stakeholders – Business needs – Business/project objectives – Functional/non‐functional requirements – Acceptance criteria – Business rules – Impacts to other areas of organization – Support & training requirements – Assumptions & constraints Guide to PMBOK © Mohammad A. Rajabi 12 Outputs • Requirements Management Plans – – – – – How requirement activities are planned, planned tracked & reported Configuration Management Requirement prioritization Product metrics Traceability structure • Requirements Traceability Matrix – – – – – – – Business needs, opportunities, goals, objectives Project objectives Project scope/WBS deliverables Product design Product development Test strategy/test scenarios High‐level requirements to more detailed requirements Guide to PMBOK © Mohammad A. Rajabi 13 5 2 Define Scope 5.2 Guide to PMBOK © Mohammad A. Rajabi 14 Data Flow Guide to PMBOK © Mohammad A. Rajabi 15 Inputs • Project charter • Requirements documentation • Organizational Process Assets – Policies, procedures, templates – Project j files from p past p projects j – Lesson learned Guide to PMBOK © Mohammad A. Rajabi 16 Tools & Techniques • Expert E t jjudgment d t – – – – – – Other units in the organization Consultants Stakeholders Professional/technical associations Industry groups Subject matter experts • Product analysis • Alternatives identification • Facilitated workshops Guide to PMBOK © Mohammad A. Rajabi 17 Outputs • Project P j t scope statement t t t – – – – – – Scope description Acceptance criteria Deliverables Exclusions Constraints Assumptions • Project document updates – Stakeholder register – Requirements documentation – Requirements q traceabilityy matrix Guide to PMBOK © Mohammad A. Rajabi 18 5 3 Create WBS 5.3 Guide to PMBOK © Mohammad A. Rajabi 19 Data Flow Guide to PMBOK © Mohammad A. Rajabi 20 Inputs • Project scope statement • Requirements documentation • Organizational process assets – Policies, procedures, templates – Project j files from p past p projects j – Lesson learned Guide to PMBOK © Mohammad A. Rajabi 21 Tools &Techniques • Decomposition – Identifying y g and analyzing y g deliverables – Structuring and organizing the WBS – Decomposing high high‐level level WBS into low low‐level level components – Developing l i and d assigning i i id identification ifi i codes d – Verifying the degree of decomposition Guide to PMBOK © Mohammad A. Rajabi 22 Sample WBS (by work package) Guide to PMBOK © Mohammad A. Rajabi 23 Sample WBS (by phase) Guide to PMBOK © Mohammad A. Rajabi 24 Sample WBS (by deliverables) Guide to PMBOK © Mohammad A. Rajabi 25 Outputs • WBS • WBS dictionary – – – – – – – – – – – Code of identifier Description of work Responsible organization Li off scheduled List h d l d milestone il Associated schedule activities Resources required q Cost estimates Quality requirements A Acceptance t criteria it i Technical references Contract information Guide to PMBOK © Mohammad A. Rajabi 26 Outputs • Scope baseline – Project j scope p statement – WBS – WBS dictionary • Project document updates Guide to PMBOK © Mohammad A. Rajabi 27 5 4 Verify Scope 5.4 Guide to PMBOK © Mohammad A. Rajabi 28 Data Flow Guide to PMBOK © Mohammad A. Rajabi 29 Inputs • Project Management Plan – Project j scope p statement – WBS – WBS dictionary • Requirement Documentation • Requirement traceability Matrix • Validated deliverables Guide to PMBOK © Mohammad A. Rajabi 30 Tools & Techniques • Inspection – Measuring, g, examining, g, verifying y g work vs. requirements & acceptable criteria Guide to PMBOK © Mohammad A. Rajabi 31 Outputs • Acceptable deliverables • Change requests • Project document updates Guide to PMBOK © Mohammad A. Rajabi 32 Control Scope Guide to PMBOK © Mohammad A. Rajabi 33 Data Flow Guide to PMBOK © Mohammad A. Rajabi 34 Inputs • Project P j t managementt plan l – – – – – • • • • Scope baseline Scope management plan Change management plan Configuration management plan Requirement management plan Work performance information Requirements documentation Requirements traceability matrix Organizationall process assets – Existing formal/informal scope control policies, procedures – Monitoring/reporting methods Guide to PMBOK © Mohammad A. Rajabi 35 Tools & Techniques • Variance analysis – Determiningg cause and degree g of variance vs. scope baseline – Corrective/preventive actions Guide to PMBOK © Mohammad A. Rajabi 36 Outputs • Work W k performance f measurements t • Organizational Process Assets updates – Causes off variances – Corrective action chosen, reasons – Lesson learned • Change requests • Project P j t managementt plan l updates d t – Scope baseline updates – Other baseline (cost, (cost schedule, schedule …)) updates • Project document updates Guide to PMBOK © Mohammad A. Rajabi 37