|
Event Chain Diagrams are visualizations that show the relationships between events and tasks and how the events affect each other.
Event chain diagram are uintroduced as a part of Event chain methodology. Event chain methodology is an uncertainty modeling and schedule network analysis technique that is focused on identifying and managing events and event chains that affect project schedules. Event chain methodology is the next advance beyond critical path method and critical chain project management. Event chain diagram Event chain methodology is an uncertainty modeling and schedule network analysis technique that is focused on identifying and managing events and event chains that affect project schedules. ...
Network analysis is the analysis of networks through network theory (or more generally graph theory). ...
A project is a temporary endeavor undertaken to create a unique product or service[1]. // The word project comes from the Latin word projectum from projicere, to throw something forwards which in turn comes from pro-, which denotes something that precedes the action of the next part of the word...
The Critical Path Method, abbreviated CPM, is a mathematically based algorithm for scheduling a set of project activities. ...
Critical Chain Project Management (CCPM) is based on methods and algorithms developed in 1997 by Eliyahu M. Goldratt. ...
Event chain diagrams are presented on the Gantt chart according to the specification. This specification is a set of rules, which can be understandable by anybody using this diagram: Gantt chart showing three kinds of schedule dependencies (in red) and percent complete indications. ...
1. All events are shown as arrows. Names and/or IDs of events are shown next to the arrow.
2. Events with negative impacts (risks) are represented by down arrows; events with positive impacts (opportunities) are represented by up arrows.
3. Individual events are connected by lines representing the event chain.
4. A sender event with multiple connecting lines to receivers represents multicasting.
5. Events affecting all activities (global events) are shown outside Gantt chart. Threats are shown at the top of the diagram. Opportunities are shown at the bottom of the diagram.
Often event chain diagrams can become very complex. In these cases, some details of the diagram do not need to be shown. Here is a list of optional rules for event chain diagrams:
1. Horizontal positions of the event arrows on the Gantt bar correspond with the mean moment of the event.
2. Probability of an event can be shown next to the event arrow.
3. Size of the arrow represents relative probability of an event. If the arrow is small, the probability of the event is correspondingly small.
4. Multiple diagrams may be required to represent different event chains for the same schedule.
5. Different colors can be use to represent different events (arrows) and connecting lines associated with different chains.
The central purpose of event chain diagrams is not to show all possible individual events. Rather, event chain diagrams can be used to understand the relationship between events. Therefore, it is recommended the event chain diagrams be used only for the most significant events during the event identification and analysis stage. Event chain diagrams can be used as part of the risk identification process, particularly during brainstorming meetings. Members of project teams can draw arrows between associated with activities on the Gantt chart. Event chain diagrams can be used together with other diagramming tools.
The simplest way to represent these chains is to depict them as arrows associated with certain tasks or time intervals on the Gantt chart. Different events and event chains can be displayed using different colors. Events can be global (for all tasks in the project) and local (for a particular task). By using Event Chain Diagrams to visualize events and event chains, the modeling and analysis of risks and uncertainties can be significantly simplified.
See also
PERT (Program Evaluation and Review Technique) charts were first developed in the 1950s by the US Navy to help manage very large, complex projects (such as Polaris) with a high degree of intertask dependency. ...
Gantt chart showing three kinds of schedule dependencies (in red) and percent complete indications. ...
A simple run chart showing data collected over time. ...
External links - Event Chain Methodology in Details
| 
Feeds |
Contact