Network Diagrams and Schedule Analysis
Network Diagrams and schedule analysis
NETWORK DIAGRAMS ARE SCHEMATIC DISPLAYS OF PROJECT SCHEDULE ACTIVITIES AND THE INTERDEPENDENCIES BETWEEN THESE ACTIVITIES. WHEN DEVELOPED PROPERLY, THIS GRAPHICAL VIEW OF A PROJECT’S ACTIVITIES CONVEYS CRITICAL SCHEDULE CHARACTERISTICS REQUIRED TO EFFECTIVELY ANALYZE AND ADJUST SCHEDULES – THUS RESULTING IN ACCURATE AND FEASIBLE SCHEDULES. THIS DOCUMENT ADDRESSES WHAT SHOULD BE CONSIDERED IN THE DEVELOPMENT OF A NETWORK DIAGRAM, HOW NETWORK DIAGRAMS ARE CREATED, AND HOW THEY MAY BE ANALYZED TO IDENTIFY NECESSARY CORRECTIVE ACTIONS AND ENSURE OPTIMAL SCHEDULE DEFINITION.
Network Diagram Creation
Network diagrams can be created manually but are also available as project views in project scheduling tools such as Microsoft Project. (See Microsoft Project, View→ More Views → Network Diagram).
Inputs: • Project Scope Statement – The schedule definition required in network diagram development must be based on the approved scope documented in the Project Scope Statement. If network diagram and schedule definition does not account for all required deliverables in scope, the resulting network diagram and schedule will not accurately reflect the time necessary to complete the work. • Work Breakdown Structure (WBS) – The Project Team must include WBS project work in the network diagram to ensure comprehensive reflection of project activities. • Historical Project Information – The accuracy of network diagram/schedule estimation is strengthened by actual schedule metrics from past projects. Project teams should consider past level of effort and duration for comparable project activities. • WBS Dictionary – The WBS Dictionary defines task durations, dependencies, predecessor and successor relationships, and resources – all of which need to be defined prior to network diagram creation to ensure that the network diagram accurately reflects the schedule required to successfully complete the project. • Resource
NETWORK DIAGRAMS ARE SCHEMATIC DISPLAYS OF PROJECT SCHEDULE ACTIVITIES AND THE INTERDEPENDENCIES BETWEEN THESE ACTIVITIES. WHEN DEVELOPED PROPERLY, THIS GRAPHICAL VIEW OF A PROJECT’S ACTIVITIES CONVEYS CRITICAL SCHEDULE CHARACTERISTICS REQUIRED TO EFFECTIVELY ANALYZE AND ADJUST SCHEDULES – THUS RESULTING IN ACCURATE AND FEASIBLE SCHEDULES. THIS DOCUMENT ADDRESSES WHAT SHOULD BE CONSIDERED IN THE DEVELOPMENT OF A NETWORK DIAGRAM, HOW NETWORK DIAGRAMS ARE CREATED, AND HOW THEY MAY BE ANALYZED TO IDENTIFY NECESSARY CORRECTIVE ACTIONS AND ENSURE OPTIMAL SCHEDULE DEFINITION.
Network Diagram Creation
Network diagrams can be created manually but are also available as project views in project scheduling tools such as Microsoft Project. (See Microsoft Project, View→ More Views → Network Diagram).
Inputs: • Project Scope Statement – The schedule definition required in network diagram development must be based on the approved scope documented in the Project Scope Statement. If network diagram and schedule definition does not account for all required deliverables in scope, the resulting network diagram and schedule will not accurately reflect the time necessary to complete the work. • Work Breakdown Structure (WBS) – The Project Team must include WBS project work in the network diagram to ensure comprehensive reflection of project activities. • Historical Project Information – The accuracy of network diagram/schedule estimation is strengthened by actual schedule metrics from past projects. Project teams should consider past level of effort and duration for comparable project activities. • WBS Dictionary – The WBS Dictionary defines task durations, dependencies, predecessor and successor relationships, and resources – all of which need to be defined prior to network diagram creation to ensure that the network diagram accurately reflects the schedule required to successfully complete the project. • Resource