Chap 5.6 Control Scope
6 likes810 views
The document discusses the Control Scope process from the Project Management Body of Knowledge (PMBOK). It defines control scope as monitoring the project and product scope and managing changes to the scope baseline. It describes inputs like project documents and work performance data. Techniques include variance analysis to determine differences from the baseline and trend analysis using earned value. Outputs include change requests, updates to project documents and the project management plan, and work performance information. The goal is to avoid uncontrolled scope creep by managing changes through an integrated change control process.
Chap 5.6 Control Scope
- 1. Chapter 5 – Project Scope Management Control Scope PMP Trainer: Anand BobadePMBOK 6th Edition, 2019, All rights reserved. SIXTH EDITION
- 2. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) 5.6 Control Scope Process overview Scope creep Control scope Process Definition Control scope - ITTO What is variance analysis? What is Trend analysis? Review
- 3. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Scope Management processes Plan scope management Collect Requirements Define Scope Create WBS Validate Scope Control Scope P P P MC MCP
- 4. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Control Scope -> Overview Monitor & Control Project work Avoid scope creep Perform Integrated change control
- 5. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Change is inevitable; therefore some type of change control process is mandatory for every project Controlling project scope ensures all requested changes & recommended corrective or preventive actions are processed through the Perform Integrated Change Control process Control Scope is also used to manage the actual changes when they occur and is integrated with the other control processes. Control Scope -> Overview
- 6. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources is referred as SCOPE CREEP. Poorly defined requirement s Lack of stakeholder engagement Not managing scope baselines Poor Change control process Control Scope -> Scope creep
- 7. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Monitoring the status of the project and product scope and managing changes to the scope baseline It allows the scope baseline to be maintained throughout the project. Control Scope process definition Monitoring status of Project Monitor product scope Manage changes to scope baseline
- 8. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Data Analysis Project Management plan Project Documents Work Performance Data Organizational process assets Work Performance Information Change Request PMP Updates Project Documents updates Inputs Tools & Techniques Outputs Control Scope Process ->ITTO
- 9. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Project Management plan Project Documents Work Performance Data Organizational process assets Control Scope -> Input
- 10. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Project Management plan Following subsidiary plans & baseline will provide key input: Control Scope -> Input -> Project Management plan Scope Management plan Requirements Management plan Scope baseline Change Management plan Configuration Management plan Performance measurement baseline
- 11. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Project Documents Following Project Documents will provide key input: Control Scope -> Input -> Project Documents Requirements Documentation Req. Traceability Matrix Lessons Learned Register
- 12. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Work Performance Data The scope completed or No of deliverables produced, in the last reporting period goes into the work performance data. Following WPD can be obtained from Change log: No of Change request received No of request accepted Control Scope -> Input -> Work Performance Data
- 13. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Organizational process assets The OPAs that can influence control scope process include Control Scope -> Input -> Organizational process assets Policies, Procedures & guidelines Monitoring & reporting templates
- 14. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Data Analysis Control Scope -> Tools & Techniques
- 15. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Data Analysis The two data analysis techniques are: Control Scope -> T & T -> Data Analysis Variance analysis Trend analysis
- 16. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Data Analysis Variance analysis: • Performance measurement • Determine cause & degree of difference between baseline & actual performance. • Helps deciding whether corrective or preventive action is required. Control Scope -> T & T -> Data Analysis -> Variance analysis - No. of deliverables completed - Completed scope - Completed activities/work packages - Plans - Scope - WBS - PMP - Schedule
- 17. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Data Analysis Trend analysis: • Comparison current performance with performance measurement baseline though Earned Value Analysis. Determine, if performance is improving or deteriorating Examines project performance over time (EVM) Control Scope -> T & T -> Data Analysis -> Trend analysis
- 18. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Control Scope -> Outputs Work Performance Information Change Request PMP Updates Project Documents updates
- 19. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Work Performance Information How the project scope is performing compared to scope baseline. How they impact schedule & cost, forecast future scope performance. Control Scope -> Outputs -> Work Performance Information
- 20. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Change Request Change request will be raised to: fix project scope to fit the plan Change plan to fit the project scope Present Nonconformities Corrective action Future Nonconformities Preventive action Past Nonconformities Defect repair Corrective action Preventive action Defect repair Control Scope -> Outputs -> Change Request
- 21. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Change Request Control Scope -> Outputs -> Change Request Corrective action: •Variance is corrected and the project scope can continue as planned. • E.g., add temporary resource to recover from delay. Preventive action: •Potential variance in the future is prevented by reversing trend in the performance baseline. •E.g., add resource to ensure timely completion of work to avoid future delay. Defect repair: •Variance is repaired and project scope can continue as planned. •E.g., Additional test cycle to ensure all defects are fixed & tested.
- 22. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) PMP Updates Following PMP components may get updated. Control Scope -> Outputs -> PMP Updates Scope Management plan Scope Baseline Schedule Baseline Cost Baseline Performance measurement baselines
- 23. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Project Documents updates Control Scope -> Outputs -> Project Documents updates Following Project Documents may get updated. Lessons Learned Register Requirements documentation Requirements Traceability Matrix
- 24. PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com) Control Scope -> Review Process overview Scope creep Control scope Process Definition Control scope - ITTO What is variance analysis? What is Trend analysis? Review