SAB4#53_Sequence Activities

Nota:

• The main product of this process is the network diagram

1. Schedule management plan

   Nota:

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

   Nota:

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

   Nota:

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

   Nota:

   • 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.
10. Define leads and lags

    Nota:

    • 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
11. Project schedule network diagram

    Nota:

    • Determine the critical path through the project.
12. Project document updates
    1. Activity attributes updates
    2. Risk Register Updates
    3. Activity list updates
13. Process group: Planning
14. Knowledge area: Time management