SAB4#53_Sequence Activities

Description

Mind Map on SAB4#53_Sequence Activities, created by pmpcertificacion on 02/14/2015.
pmpcertificacion
Mind Map by pmpcertificacion, updated more than 1 year ago
pmpcertificacion
Created by pmpcertificacion about 11 years ago
5
0

Resource summary

SAB4#53_Sequence Activities

Annotations:

  • The main product of this process is the network diagram
  1. Schedule management plan

    Annotations:

    • The plan will list any methodologies or tools you planned to use when sequencing.
    1. Activity list
      1. Activity attributes

        Annotations:

        • This includes information about each activity, including known predecessors and successors.
        1. Project scope statement
          1. Enterprise environmental factors
            1. Organizational process assets
              1. Milestone list
                1. Diagram the relationship between activities

                  Annotations:

                  • 1.- One way to visualize the way activities relate is to create a network diagram. 2.- Network diagrams put your tasks in perspective.
                  1. Define dependencies

                    Annotations:

                    • Dependencies help you sequence your activities.
                    • Finish to Start (FS): When you think of dependencies, this is what you usually think of—one thing needs to end before the next can begin.
                    • Start to Start (SS): This is a little less common, but sometimes you need to coordinate activities so they begin at the same time.
                    • Finish to Finish (FF): These two finish at the same time.
                    1. Define leads and lags

                      Annotations:

                      • Leads and lags add time between activities.
                      • 1.- A lead is when you let a task get started before its predecessor is done. 2.- Is when you give a successor task some time to get started before the predecessor finishes
                      • 1.- A lag means making sure that one task waits awhile before it gets started. 2.- Is when you purposefully put a delay between the predecessor task and the successor
                      1. Project schedule network diagram

                        Annotations:

                        • Determine the critical path through the project.
                        1. Project document updates
                          1. Activity attributes updates
                            1. Risk Register Updates
                              1. Activity list updates
                              2. Process group: Planning
                                1. Knowledge area: Time management
                                  Show full summary Hide full summary

                                  Similar