1. Chapter 5 Defining and Managing Project and Product Scope Copyright 2012 John Wiley & Sons, Inc. 5-1

2. Project Planning Framework 5-2 Copyright 2012 John Wiley & Sons, Inc.

3. What is Project Scope Management? 3

4. PMI: Project Scope Management Processes 4 Process GroupIntegration Management Process Major Output Planning P1: Plan Scope Management Scope Mgmt Plan Requirement Mgmt Plan P2: Collect Requirements Req. Documentation Req. Traceability Matrix P3: Define Scope Project Scope Stmt Project Docs Update P4: Create WBS Scope Baseline Project Docs Update Monitoring and Controlling MC1: Validate Scope Accept Deliverables Change Requests Work Performance Info MC2: Control Scope Change Requests Project Mgmt Plan Updates Org, Process Asset Updates

5. Scope Management Plan Collect Requirements  Defining and documenting the customer, sponsor, or stakeholder needs and expectations. This may be a formal document. Define Scope  A detailed description of the product, service, or information system to be designed, built and implemented. A detailed scope statement defines what work will and will not be part of the project and will serve as a basis for all future project decisions Create the Work Breakdown Structure  The decomposition or dividing of the major project deliverables (i.e., scope) into smaller and more manageable components Verify Scope  Confirmation and formal acceptance that the project’s scope is accurate, complete, and supports the project’s MOV. The project team and sponsor must agree to all deliverables Control Scope  Ensuring that controls are in place to manage proposed scope changes once the project’s scope is set. Must be communicated to all project stakeholders. 5-5

6. Scope Management Plan Collect Requirements Centers on defining and documenting the stakeholders’ needs to properly manage expectations Define Scope A detailed description of project and the product. It should define what work will and will not be included in the project. Create Work Breakdown Structure (WBS) The decomposition or dividing of the major project deliverables into smaller and more manageable components. Verify Scope Confirmation and formal acceptance that project’s scope is accurate, complete, and supports the project’s goal. Control ScopeEnsuring that controls are in place to manage proposed scope changes one the project’s scope is accepted. These procedures must be communicated and understood by all project stakeholders. 5-6

7. Scope Planning Why do we need scope planning? 5-7

8. Scope Planning 5-8 Copyright 2012 John Wiley & Sons, Inc.

9. Scope Boundary 5-9 Copyright 2012 John Wiley & Sons, Inc.

10. Planning Scope Management The project team uses expert judgment and meetings to develop two important outputs The scope management plan is a subsidiary part of the project management plan 10

11. Scope Management Plan Contents 11 Example AExample B

12. Requirements Management Plan (RMP) “conditions or capabilities that must be met by the project or present in the product, service, or result to satisfy an agreement or other formally imposed specification*” *The PMBOK® Guide, Fifth Edition

13. RMP: Collecting Requirements For some IT projects, it is helpful to divide requirements development into categories called elicitation, analysis, specification, and validation 13 http://www.certified-re.de/en/home.html

14. Relative Cost to Correct a Software Requirement Defect 14

15. RMP: Methods for Collecting Requirements 15

16. Statistics on Requirements for Software Projects * 88% of the software projects involved enhancing existing products instead of creating new ones 86% said that customer satisfaction was the most important metric for measuring the success of development projects 83% of software development teams still use MS Office applications (e.g. Word and Excel) as their main tools to communicate requirements *John Simpson, “2011: The State of Requirements Management” (2011).

17. PM Network: The Blame Game 17

18. Improving User Input 18

19. Improving User Input 19

20. Reduce Incomplete and Changing Requirements 20

21. RMP: Managing Requirements during Project A requirements traceability matrix (RTM) is a table that lists requirements, various attributes of each requirement, and the status of the requirements to ensure that all requirements are addressed 21 Another Example

22. SMP: Defining Scope Project scope statements should include at least: 22

23. Scope Boundary 5-23

24. Statement of Work  Narrative description of the product, service, or information system.  For internal projects, this is tied to the business need  For external projects, this would include specifications, quantities, quality standards, and performance requirements for prospective bidders.

25. Scope Statement 1. Develop a proactive electronic commerce strategy that identifies the processes, products and services to be delivered through the World Wide Web. 2. Develop an application system that supports all of the processes, products, and services identified in the electronic commerce strategy. 3. The application system must integrate with the bank’s existing enterprise resource planning system. 5-25

26. Out of Scope 1. Technology and organizational assessment of the current environment 2. Customer resource management and data mining components 5-26