Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 11 views

    Lesson 7

    Uploaded by

    Arif Ud Din
    This document discusses project planning and scope management. It provides an overview of key scope management processes including scope planning, definition, verification and control. It describes tools that can be used for project-oriented scope definition such as a deliverable definition table and deliverable structure chart. For product-oriented scope definition, it discusses using context dataflow diagrams and use case diagrams. The document also provides an example scope statement and scope verification checklist. The overall summary is that the document outlines best practices and tools for defining, verifying and controlling project scope which is a critical part of project planning.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Lesson 7

    Uploaded by

    Arif Ud Din
    11 views30 pages
    This document discusses project planning and scope management. It provides an overview of key scope management processes including scope planning, definition, verification and control. It describes tools that can be used for project-oriented scope definition such as a deliverable definition table and deliverable structure chart. For product-oriented scope definition, it discusses using context dataflow diagrams and use case diagrams. The document also provides an example scope statement and scope verification checklist. The overall summary is that the document outlines best practices and tools for defining, verifying and controlling project scope which is a critical part of project planning.

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses project planning and scope management. It provides an overview of key scope management processes including scope planning, definition, verification and control. It describes tools that can be used for project-oriented scope definition such as a deliverable definition table and deliverable structure chart. For product-oriented scope definition, it discusses using context dataflow diagrams and use case diagrams. The document also provides an example scope statement and scope verification checklist. The overall summary is that the document outlines best practices and tools for defining, verifying and controlling project scope which is a critical part of project planning.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    11 views30 pages

    Lesson 7

    Uploaded by

    Arif Ud Din
    This document discusses project planning and scope management. It provides an overview of key scope management processes including scope planning, definition, verification and control. It describes tools that can be used for project-oriented scope definition such as a deliverable definition table and deliverable structure chart. For product-oriented scope definition, it discusses using context dataflow diagrams and use case diagrams. The document also provides an example scope statement and scope verification checklist. The overall summary is that the document outlines best practices and tools for defining, verifying and controlling project scope which is a critical part of project planning.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 30

    Quick Recap

    The Project Plan


    Plan Your Work, then Work Your Plan
    Project Plan
    Project Authorization
    (Project Charter)

    Project Scope

    Solutions Architecture

    Integrated Management Control Plan


    Scope Management Plan
    Time (Schedule) Management Plan
    Cost (Budget) Management Plan
    Quality Management Plan
    Project Human Resource (Team) Management Plan
    Communication Management Plan
    Risk Management Plan
    Procurement (and Contract) Management Plan

    Project Performance Baseline


    Time (Schedule) Estimates
    Cost (Budget) Estimates

    Supporting Documentation
    Lesson 3: Planning Project Work

    Topic 3B: Document Stakeholder Requirements


    Topic 3C: Create a Scope Statement
    Key stakeholders Requirements

    • Project Manager – the individual responsible for handling the project


    • Customer – the individual or organisation who will use the project’s product
    • Performing Organisation – the enterprise whose employee’s are most
    directly involved in doing the work of the project
    • Project Team Members - the group that is performing the work of the
    project
    • Project Sponsor- the individual or group that provides the resources for the
    project
    • Regulatory or government agencies
    • Sellers and contractors
    • Individual citizens or groups of citizens
    Key stakeholders Requirements

    • Each requirement will act as a Monitoring device for any change


    • Requirements should be clearly defined
    • If any change in requirement, Change control system should be
    followed
    • Requirements will be a baseline for scope development
    • Interviews, Questioners, project charter, meetings etc. will be used for
    requirements gathering
    Scope

    The deliverables or work products that must be completed in order to achieve the
    project’s MOV.

    Provides a boundary so that what needs to get done – gets done.

    Otherwise, schedule and budget are increased

    Defines what is part of the project team’s work and what is not.

    Provides a link between the project’s MOV and the project plan.
    Project Planning Framework

    MOV

    Scope

    Phases Sequence
    Schedule

    Tasks Resources

    Time Budget
    Estimates
    PMBOK Scope Management Processes
    Scope Management Description
    Process
    Scope Planning
    The development of a scope management plan that defines the project’s scope and how
    it will be verified and controlled throughout the project.

    Scope Definition A detailed scope statement that defines what work will and will not be part of the project
    and will serve as a basis for all future project decisions

    Create Work Breakdown The decomposition or dividing of the major project deliverables into smaller
    Structure (WBS) and more manageable components.

    Scope Verification Confirmation and formal acceptance that the project’s scope is accurate,
    complete, and supports the project’s MOV.

    Scope Change Control Ensuring that controls are in place to manage proposed scope changes once the
    project’s scope is set. These procedures must be communicated to all project
    stakeholders.
    Scope Management Plan

    Scope
    Scope Scope Scope
    Definition Create WBS
    Planning Verification Control

    Project Formalized Defined


    Builds upon
    Documents planning acceptance process for
    preliminary
    how team tool from managing
    scope stmt
    will define subdivides appropriate changes &
    to define all
    & develop the scope stakeholders impact to
    project and
    project into tat defined budget &
    product
    scope. deliverable scope schedule
    deliverables
    hierarchy complete

    Scope Change
    Detailed Verification
    management WBS control
    scope checklist
    plan process
    Problems with Scope
    • Ambiguous
    Ambiguity in scope leads to confusion and unnecessary work.
    • Incomplete
    Incomplete scope leads to schedule slips and hence finally cost overrun.
    • Transient
    Transient scope leads to what is known as scope creep which is the primary cause
    of late deliveries and potentially "never ending" projects.
    • Un-collaborative
    A scope that is not collaborated leads to misinterpretations in requirements and
    design.
    Capture Project Scope Success

    • Define the project need

    • Identify key stakeholders

    • Identify project drivers

    • Develop operational concepts

    • Identify external interfaces


    Project Scope Initiation & Planning
    • A beginning process that formally authorizes the project manager and team to
    develop the scope management plan

    • This entails
    • Conceptualizing the Scope Boundary
    • Developing the Scope Statement
    The Scope Boundary

    “Failure to define what is part of the project, as well as what is not, may
    result in work being performed that was unnecessary to create the product
    of the project and thus lead to both schedule and budget overruns.”

    - Olde Curmudgeon, 1994


    The Scope Statement

    • Provides a way to define the scope boundary.

    • A narrative of what deliverables or work-products the project team will and will
    not provide throughout the project.

    • A first step that provides a high-level abstraction of the project’s scope that will
    be defined in greater detail as the project progresses.
    Scope Statement Example – Work within the scope boundary

    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.
    Scope Statement Example – Work outside the scope boundary

    1. Technology and organizational assessment of the current environment

    2. Customer resource management and data mining components


    Project Scope Definition
    • Project-Oriented Scope
    • Deliverables that support the project management and IT development
    processes defined in the Information Technology Project Methodology (ITPM).
    • Examples : Business case, project charter and project plan, etc.
    • Product-Oriented Scope
    • High-level features and functionality of the application system
    • First cut for requirements definition that will be defined in greater detail during the
    systems development life cycle (SDLC)
    • Examples : Add new customer, look up customer balance, print daily sales
    report by region, etc.
    Project-Oriented Scope Definition Tools

    • Deliverable Definition Table (DDT)


    • Deliverable Structure Chart (DSC)
    Deliverable Definition Table
    Deliverable Structure Standards Approval Resources
    Needed By Required
    Business Case Document As defined in project Project Sponsor Business Case
    methodology team & OA tools

    Project charter & Document As defined in project Project Sponsor Project manager,
    project plan methodology sponsor, & OA
    tools

    Technology & Document As defined in project Project manager Bank’s syst.


    Org. assessment methodology & Sponsor analyst, OA & case
    tools

    Requirements Document As defined in project Project manager Syst. analyst


    definition methodology programmer
    Case & OA
    Deliverable Structure Chart
    Product-Oriented Scope Definition Tools

    • Context Dataflow Diagram (DFD)


    • Use Case Diagram (USD)
    Scope Verification
    • Ensures:
    • That the project’s scope is well-defined, accurate and complete
    • The project’s scope is acceptable to the project stakeholders
    • That standards exist so that the project’s scope will be completed correctly
    • That the project’s MOV will be achieved if the project scope is completed
    • Tools
    • Scope Verification Checklist
    Scope Verification Check List

     MOV – Has the project’s MOV been clearly defined and agreed upon?
     Deliverables – Are the deliverables tangible and verifiable? Do they support the project’s MOV?
     Quality Standards - Are controls in place to ensure that the work was not only completed but also
    completed to meet specific standards?
     Milestones – Are significant events that mark the acceptance of a deliverable and give the project
    manager and team the approval to begin working on the next deliverable
     Review and Acceptance
    Scope Change Control
    • Ensures that any changes to the project’s scope will help
    the project achieve its MOV.

    • Keeps the “triple constraint” in balance.


    Scope Change Control

    • Mitigates:

    • Scope Grope – i.e., scope poorly defined


    • Scope Creep – i.e., increasing featurism
    • Scope Leap – i.e., drastic change in project direction or the project’s MOV

    • Tools:
    • Scope Change Request Form
    • Scope Change Request Log
    Example of a Scope Change Request Form
    Example of a Scope Change Request Log
    Benefits of Scope Control

    • Keeps the project manager in control of the project.

    • Gives the project manager the authority to manage and control the project’s
    schedule and budget. Otherwise she or he may ‘feel” pressured by the client or
    upper management to accept scope changes

    • Allows the project team to stay focused and on track

    • Do not have to perform unnecessary work


    Summary of Scope Management Processes

    You might also like