Project Management 3 Scope Management

2,500 views
2,264 views

Published on

This is the 3rd presentation as part of PM Awareness Sessions I\'ve made for my company\'s (ITEC) staff to increase their awareness of PM best practices.

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,500
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Project Management 3 Scope Management

  1. 1. Project Management<br />Scope Management<br />MOHAMMAD K. KIWAN<br />PMO MANAGER<br />IMAGE TECHNOLOGIES<br />Part of Project Management Awareness Sessions<br />
  2. 2. Scope – What is it?<br />Scope is simply what you will produce (Product Scope) or the work you will put in order to produce it (Project Scope)<br />Defining scope is usually the first step in planning. Time, cost & quality follows.<br />Jul. 6th, 2009<br />2<br />
  3. 3. The triple constraint<br />Every project is constrained in different ways by its:<br />Scope: What work will be done as part of the project? What unique product, service, or result does the customer or sponsor expect from the project?<br />Time: How long should it take to complete the project? What is the project’s schedule?<br />Cost: What should it cost to complete the project? What is the project’s budget?<br />Jul. 6th, 2009<br />3<br />
  4. 4. The triple constraint triangle<br />Jul. 6th, 2009<br />4<br />Scope<br />Time<br />Quality<br />Cost<br />
  5. 5. Work Breakdown Structure (WBS)<br />The most important scope planning tool.<br />The idea is to divide (breakdown) work into pieces.<br />The WBS should contain all the work (no less) and only the work needed (no extra)<br />Jul. 6th, 2009<br />5<br />
  6. 6. WBS (more)<br />It is generally correct that “If it is not in the WBS, we should not do it”<br />WBS should generally be deliverable-oriented and not task oriented.<br />It has many approaches: Phase, Product breakdown, objectives, deliverables, … depending on the business and project.<br />Jul. 6th, 2009<br />6<br />
  7. 7. WBS (more)<br />WBS can be in chart (preferred) or in tabular format.<br />Usually we use MS Visio to make the chart format, and MS Project (or excel in initial stages) to make the tabular format.<br />Jul. 6th, 2009<br />7<br />
  8. 8. WBS chart & tabular example<br />Jul. 6th, 2009<br />8<br />
  9. 9. Jul. 6th, 2009<br />9<br />
  10. 10. Where/When to capture Scope<br />Product Scope<br />Statement of Work (Contract, proposal, …)<br />Project Initiation Document (PID)<br />Software Requirements Specifications (SRS) or any product specifications document.<br />Final Product Scope is usually captured during requirements collection phase.<br />Jul. 6th, 2009<br />10<br />
  11. 11. Where/When to capture Scope<br />Project Scope<br />Scope Statement<br />WBS & WBS Dictionary<br />Project Schedule & Plan<br />Task Sheets<br />You must create a scope baseline<br />Project Scope is created in Planning phase.<br />Jul. 6th, 2009<br />11<br />
  12. 12. Scope Control<br />Scope control means you make sure only the approved work is done, and approved product is being made.<br />You control scope to avoid scope creep.<br />Scope creep can be from inside or outside the project team<br />If scope has to change -&gt; Change Process<br />Jul. 6th, 2009<br />12<br />
  13. 13. Questions?<br />Jul. 6th, 2009<br />13<br />
  14. 14. Thank You<br />Jul. 6th, 2009<br />14<br />

×