Developing a Project Plan

Developing a Project Plan

1. Project Network

   • It's a flowchart
     • always going left to right like a paper
       • Nothing crazy
     • logical sequence
       • Start and end time of each task
       • shows what tasks are critical
       • Activity's
         • Merge activity
           • needs other activities to be done for it to be compeleted
         • Burst, once one is completed, many others can be done
           • AON
             • Activity on node network
               • Includes details, a legend, and a solid plan
       • Critical Path
         • The longest path to compeletion
           • Try to avoid cross overs in paths
             • Not always possible, but keep crossovers to a minimum
               • not even Jordan can avoid cross overs
                 • LeBron can though
   • "ifs" are not in the diagram
     • if you have plan B's, they have their own diagram
   • Network Information
     • Define requirments
       • assign the team
         • designing the hardware
           • etc etc etc
     • The tasks always have a set time
       • May not happen in reality
         • But in the plan everything is set, not varied
           • You can also have wait to start a new segment
             • This is called "lag" days
       • Early start
         • Forward pass helps you find the earliest time you can start things
         • Early finish
           • Early finish becomes the next early start
       • Backward pass
         • The latest time you can finish things
           • Can have a set amount of slack time
             • If you have 15 days of slack time, it isnt 15 days per activity, it's 15 days in total
         • This helps you find the critical path
           • If there are any slack days on the critical path, the whole project gets delayed

Imagens e arquivos do mapa