proj mgmt 2

  • Upload
    sujro

  • View
    230

  • Download
    0

Embed Size (px)

Citation preview

  • 8/9/2019 proj mgmt 2

    1/27

    4-1

    DEFINE THE PROJECT

    Planning the Project

  • 8/9/2019 proj mgmt 2

    2/27

    4-2

  • 8/9/2019 proj mgmt 2

    3/27

    4-3

    Defining the Project

    Step 1: Defining the Project Scope

    Step 2: Establishing Project Priorities

    Step 3: Creating the Work BreakdownStructure

    Step 4: Integrating the WBS with the

    Organization

    Step 5: Coding the WBS for the Information

    System

  • 8/9/2019 proj mgmt 2

    4/27

    4-4

    Step 1: Defining the Project Scope

    Project Scope A definition of the end result or mission of the

    projecta product or service for the client/customer

    in specific, tangible, and measurable terms.

    Purpose of the Scope Statement

    To clearly define the deliverable(s) for the end user.

    To focus the project on successful completion of its

    goals.

    To be used by the project owner and participants as a

    planning tool and for measuring project success.

  • 8/9/2019 proj mgmt 2

    5/27

    4-5

    Project Scope Checklist

    1. Project objective

    2. Deliverables

    3. Milestones4. Technical requirements

    5. Limits and exclusions

    6. Reviews with customer

  • 8/9/2019 proj mgmt 2

    6/27

    4-6

    Project Scope: Terms and Definitions

    Scope Statements Also called statements of work (SOW)

    Project Charter

    Can contain an expanded version of scope

    statement

    A document authorizing the project manager to

    initiate and lead the project.

    Scope Creep

    The tendency for the project scope to expand

    over time due to changing requirements,

    specifications, and priorities.

  • 8/9/2019 proj mgmt 2

    7/27

    4-7

    Step 2: Establishing Project Priorities

    Causes of ProjectT

    rade-offs Shifts in the relative importance of criterions

    related to cost, time, and performance

    parameters

    o BudgetCosto ScheduleTime

    o PerformanceScope

    Managing the Priorities of Project Trade-offs

    Constrain: a parameter is a fixed requirement. Enhance: optimizing a parameter over others.

    Accept: reducing (or not meeting) a parameter

    requirement.

  • 8/9/2019 proj mgmt 2

    8/27

    4-8

    Project Management Trade-offs

    FIGURE 4.1

  • 8/9/2019 proj mgmt 2

    9/27

    4-9

    Project Priority Matrix

    FIGURE 4.2

  • 8/9/2019 proj mgmt 2

    10/27

    4-10

    Step 3: Creating the Work

    Breakdown StructureWork Breakdown Structure (WBS)

    An hierarchical outline (map) that identifies the

    products and work elements involved in a project

    Defines the relationship of the final deliverable

    (the project) to its subdeliverables, and in turn,

    their relationships to work packages

    Best suited for design and build projects that

    have tangible outcomes rather than process-

    oriented projects

  • 8/9/2019 proj mgmt 2

    11/27

    4-11

    Hierarchical

    Breakdownof the WBS

    FIGURE 4.3

  • 8/9/2019 proj mgmt 2

    12/27

    4-12

    Develop a WBS

    Wedding Project: Check the kundalis of bride and groom

    Get a Muhurat set fix the date

    o Fix the Purohits

    Decide the venue

    o Arrange venue

    Lighting

    Floral decorations

    Seating arrangement for

    Arrange for the ceremonies

    Order the bridal requisiteso Dresses

    o Jewellery

    Guests list

  • 8/9/2019 proj mgmt 2

    13/27

    4-13

    How WBS Helps the Project Manager

    WBS Facilitates evaluation of cost, time, and technical

    performance of the organization on a project

    Provides management with information appropriate

    to each organizational level Helps in the development of the organization

    breakdown structure (OBS), which assigns project

    responsibilities to organizational units and

    individuals Helps manage plan, schedule, and budget

    Defines communication channels and assists in

    coordinating the various project elements

  • 8/9/2019 proj mgmt 2

    14/27

    4-14

    Work Breakdown Structure

    FIGURE 4.4

  • 8/9/2019 proj mgmt 2

    15/27

    4-15

    Work Packages

    A Work Package Is the Lowest Level ofthe WBS.

    It is output-oriented in that it:

    o Defines work (what)

    o Identifies time to complete a work package (how long)

    o Identifies a time-phased budget to complete a work

    package (cost)

    o Identifies resources needed to complete a workpackage (how much)

    o Identifies a single person responsible for units of work

    (who)

  • 8/9/2019 proj mgmt 2

    16/27

    4-16

    Step 4: Integrating the WBS

    with the OrganizationOrganizational Breakdown Structure (OBS)

    Depicts how the firm is organized to discharge its

    work responsibility for a projecto Provides a framework to summarize organization

    work unit performance

    o Identifies organization units responsible for work

    packages

    o Ties the organizational units to cost control

    accounts

  • 8/9/2019 proj mgmt 2

    17/27

    4-17

    FIGURE 4.5

    Integration of WBS and OBS

  • 8/9/2019 proj mgmt 2

    18/27

    4-18

    Step 5: Coding the WBS

    for the Information SystemWBS Coding System

    Defines:

    o Levels and elements of the WBSo Organization elements

    o Work packages

    o Budget and cost information

    Allows reports to beconsolidated at any

    level in the organization structure

  • 8/9/2019 proj mgmt 2

    19/27

    4-19

    WBSCoding

  • 8/9/2019 proj mgmt 2

    20/27

    4-20

    Process Breakdown Structure

    Process-Oriented Projects Are driven by performance requirements in which the

    final outcome is the product of a series of steps of

    phases in which one phase affects the next phase

    Process Breakdown Structure (PBS) Defines deliverables as outputs required to move to

    the next phase

    Checklists for managing PBS:

    o Deliverables needed to exit one phase and begin the next

    o Quality checkpoints for complete and accurate deliverables

    o Sign-offs by responsible stakeholders to monitor progress

  • 8/9/2019 proj mgmt 2

    21/27

    4-21

    PBS for Software Project Development

    FIGURE 4.6

  • 8/9/2019 proj mgmt 2

    22/27

    4-22

    Responsibility Matrices

    Responsibility Matrix (RM) Also called a linear responsibility chart

    Summarizes the tasks to be accomplished and

    who is responsible for what on the project

    o Lists project activities and participants

    o Clarifies critical interfaces between units and individuals

    that need coordination

    o Provide an means for all participants to view theirresponsibilities and agree on their assignments

    o Clarifies the extent or type of authority that can be

    exercised by each participant

  • 8/9/2019 proj mgmt 2

    23/27

    4-23

    Responsibility Matrix for a Market

    Research Project

    FIGURE 4.7

  • 8/9/2019 proj mgmt 2

    24/27

    4-24

    Responsibility Matrix for the Conveyor

    Belt Project

    FIGURE 4.8

  • 8/9/2019 proj mgmt 2

    25/27

    4-25

    Project Communication Plan

    What information needs to be collected?

    Who will receive information?

    What information methods will be used?

    What are the access restrictions?

    When will information be communicated?

    How will information be communicated?

  • 8/9/2019 proj mgmt 2

    26/27

    4-26

    Communication Plan:

    FIGURE 4.9

  • 8/9/2019 proj mgmt 2

    27/27

    4-27

    Key Terms

    Cost account

    Milestone

    Organization breakdown structure (OBS)

    Scope creep

    Priority matrix

    Responsibility matrix

    Scope statement

    Process breakdown structure (PBS)Work breakdown structure (WBS)

    Work package