Top Banner

of 37

08 PROJECT CYCLE B

Apr 09, 2018

Download

Documents

philip_kock
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
  • 8/8/2019 08 PROJECT CYCLE B

    1/37

  • 8/8/2019 08 PROJECT CYCLE B

    2/37

    The Project CycleThe Project Cycle

  • 8/8/2019 08 PROJECT CYCLE B

    3/37

    The Project CycleThe Project Cycle

    To Get to a Plan.You Need a Network Diagram

  • 8/8/2019 08 PROJECT CYCLE B

    4/37

    The Project CycleThe Project Cycle

    The Network Diagram

    Essentially thesequencing of activities

    A tool for planning, scheduling and

    monitoring projectprogressDeveloped from the WBS

    Achart that graphicallydepicts thesequence, interdependencies, and startand finish times of the project job plan of

    activities that is the critical path through thenetwork

  • 8/8/2019 08 PROJECT CYCLE B

    5/37

    The Project CycleThe Project Cycle

    The Network Diagram

    Provides the basis for scheduling laborand equipment

    Enhances communication among project

    participants

    Provides an estimate of the projectsduration

    Provides a basis forbudgeting cash flow

    Highlights activities that are criticaland cannotbe delayed

    Help managers get and stay on plan.

  • 8/8/2019 08 PROJECT CYCLE B

    6/37

    The Project CycleThe Project Cycle

    The Network Diagram

  • 8/8/2019 08 PROJECT CYCLE B

    7/37

    The Project CycleThe Project Cycle

    Activity On Arrow

  • 8/8/2019 08 PROJECT CYCLE B

    8/37

    The Project CycleThe Project Cycle

    Activity On Node

  • 8/8/2019 08 PROJECT CYCLE B

    9/37

    The Project CycleThe Project Cycle

    Relationships/Dependencies

  • 8/8/2019 08 PROJECT CYCLE B

    10/37

    The Project CycleThe Project Cycle

    Relationships/Dependencies

  • 8/8/2019 08 PROJECT CYCLE B

    11/37

    The Project CycleThe Project Cycle

    Relationships/Dependencies

    Networks typically flow from left to right

    An activitycannotbegin untilallof itspreceding activities are complete

    Arrows indicate precedence and flowandcan cross over each other

    Identify each activity with a unique number thisnumber must be greater than its predecessors

    Looping is not allowed Conditionalstatements are notallowed

    Use common start and stop nodes.

  • 8/8/2019 08 PROJECT CYCLE B

    12/37

    The Project CycleThe Project Cycle

    Network Diagram: Step 1

  • 8/8/2019 08 PROJECT CYCLE B

    13/37

    The Project CycleThe Project Cycle

    Network Diagram: Step 2

  • 8/8/2019 08 PROJECT CYCLE B

    14/37

    The Project CycleThe Project Cycle

    Network Diagram: Step 3

  • 8/8/2019 08 PROJECT CYCLE B

    15/37

    The Project CycleThe Project Cycle

    Network Diagram: Step 4

  • 8/8/2019 08 PROJECT CYCLE B

    16/37

    The Project CycleThe Project Cycle

    Network Diagram: Step 5

    A Forward Pass through the network

    determines the earliest times each activity can

    start and finish Forward Pass:

    How soon can the activity start? (early start

    ES)

    How soon can the activity finish? (early finishEF)

  • 8/8/2019 08 PROJECT CYCLE B

    17/37

    The Project CycleThe Project Cycle

    Network Diagram: Step 5

    Add activity times along each path in thenetwork (ES+ Duration = EF)

    Carry the early finish (EF) to the nextactivitywhere itbecomes its early

    start(ES) unless The next succeeding activity is a merge

    activity, in which case the largest EF ofall preceding activities is selected.

  • 8/8/2019 08 PROJECT CYCLE B

    18/37

    The Project CycleThe Project Cycle

    Network Diagram: Step 5

  • 8/8/2019 08 PROJECT CYCLE B

    19/37

    The Project CycleThe Project Cycle

    Network Diagram: Step 6

    A Backward Pass through the networkdetermines the latest times each

    activitycan start and finish withoutdelaying completion of the project Backward Pass : How late can the activity start? (late

    startLS) How late can the activity finish? (latefinishLF)

  • 8/8/2019 08 PROJECT CYCLE B

    20/37

    The Project CycleThe Project Cycle

    Network Diagram: Step 6

    Subtract activity durations along eachpath in the network (LF- Duration =

    LS) Carry the late start(LS) to the nextactivitywhere itbecomes its latefinish (LF) unless

    The activity is a merger activity, in whichcase the smallest LS of the previousactivities is selected.

  • 8/8/2019 08 PROJECT CYCLE B

    21/37

    The Project CycleThe Project Cycle

    Network Diagram: Step 6

  • 8/8/2019 08 PROJECT CYCLE B

    22/37

    The Project CycleThe Project Cycle

    Important Concepts

    Slack(orFloat): The duration an activity can be delayed after

    the start of a longer parallel activity or activities Totalslack: The duration an activity can be delayed without

    delaying the entire project The criticalpath is the networkpath(s)

    that has (have) the least slack in common-normallyZero.

  • 8/8/2019 08 PROJECT CYCLE B

    23/37

    The Project CycleThe Project Cycle

    Important Concepts

    Utilization ofSlack: If slack in an activity on a path is

    used, the ES of all activities that followin that chain will be delayed and theirslack reduced. Use of totalslackshould therefore be coordinated

    with allparticipants in theactivities that follow in that chain

  • 8/8/2019 08 PROJECT CYCLE B

    24/37

    The Project CycleThe Project Cycle

    Important Concepts

    Free slack: Free slack, however is unique because the

    activity can be delayed without delaying the ES

    of activities following it. Free slack is defined asthe difference between the EF of an activity andthe ES of the activity that follows. Onlyactivities where that occur at the end of a chain

    of activities (usually where you have a mergeactivity) can have free slack Free slack doesnot affect the activities following it.

  • 8/8/2019 08 PROJECT CYCLE B

    25/37

    The Project CycleThe Project Cycle

    The Network Diagram In MS Project

  • 8/8/2019 08 PROJECT CYCLE B

    26/37

    JANUARY 2007

    FINAL DELIVERABLE

    SUB DELIVERABLES

  • 8/8/2019 08 PROJECT CYCLE B

    27/37

  • 8/8/2019 08 PROJECT CYCLE B

    28/37

  • 8/8/2019 08 PROJECT CYCLE B

    29/37

  • 8/8/2019 08 PROJECT CYCLE B

    30/37

  • 8/8/2019 08 PROJECT CYCLE B

    31/37

    The Project CycleThe Project Cycle

    Schedule Bar Chart (Gantt)

  • 8/8/2019 08 PROJECT CYCLE B

    32/37

    The Project CycleThe Project Cycle

    Responsibility Matrix

    r

    a

    m

    responsibility

    assignment

    matrix

  • 8/8/2019 08 PROJECT CYCLE B

    33/37

    The Project CycleThe Project Cycle

    Responsibility Matrix

    Task 1

    Task 2

    Task 3

    Task 4

    Task 5

    Task 6

    Person 1 Person 2 Person 3 Person 4

  • 8/8/2019 08 PROJECT CYCLE B

    34/37

    The Project CycleThe Project Cycle

    Responsibility Matrix

    r

    as

    ci

    responsible

    accountablesupportive

    consultedinformed

  • 8/8/2019 08 PROJECT CYCLE B

    35/37

    One and only one person can be accountable. Multiple peoplecan be responsible and certainly others can be informed and

    consulted.Source: Glen B Alleman, (2007) Responsibility Assignment Matrix, Herding Cats

    http://herdingcats.typepad.com/my_weblog/2007/02/responsibility_.html retrieved 2/8/08

  • 8/8/2019 08 PROJECT CYCLE B

    36/37

    The Project CycleThe Project Cycle

    Responsibility Matrix

  • 8/8/2019 08 PROJECT CYCLE B

    37/37