Project Management 3 Scope Management

  • 1,877 views
Uploaded 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.

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.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,877
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

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