Problems or Dangers in Using Project Networks, Essay Example

Identify and discuss some of the problems or dangers in using project networks

In order to understand the problems or dangers of using project networks it must be first understood what the project network represents and how it is built. As a frame of reference, project networks illustrate before and after relationships while the work breakdown structure shows a breakout of tasks in a hierarchal fashion. The project network would have multiple terminal elements dependent on the quantity of terminal elements required for the task. A terminal element is the lowest task in the breakout and is not further subdivided. This is the lowest action required for the primary task.

The risk of the project network comes when compiling multiple variables from multiple sources and then illustrating the entire network as one cohesive diagram. Normally, during the course of building a project network there is a designated individual that will collect all of the information from each of the other key points of contacts. These contacts could range from project managers, engineers, financial analysts or testers, just to name a few. The point of contact would be determined by which task was being accomplished along the project schedule. There is an uncontrolled risk on version control when the individual comes to gather status of the project from these multiple entities. This risk would not show up on any risk analysis or risk mitigation report due to the fact that it is being accomplished as part of someone’s roles and responsibilities for the program or portfolio. The other risk is not only the compilation of disparate data but also the validity of the data that is obtained. Depending on how the information is collected and generated the project network could be exponentially misconstrued. If there are specified tollgates and individuals are held accountable for their information, the data integrity increases and the validity of the project network result increases.  If the ad hoc requests are sent at varying times and the individuals that are providing the information do not see the activity as a value add to their project or their project activities the integrity of the information will suffer.  A major concern or problem with project networks is the data validity that occurs within the network creation.

In addition to the data validity another danger is for leadership to view this easily understandable chart and create their own assumptions and decisions based on the interdependencies of the elements on the chart.  If the information that was gathered did not have the greatest validity possible and leadership received this information, with or without the person who provided it, the entire project schedule managed by the project manager could be compromised based on data that was not fully incorporated into the project plan.  This disparate information would cause misunderstanding and havoc within the project teams.  The bottom line would be that leadership expects a certain outcome while the project team is working toward another expectation.  Disparity in information leads to conflicting goal achievement and potential failure before the activity begins.

With project networks, the major concern or problem lies within the data that is collected and implemented into the diagram.  In order to mitigate the problem with data validity and coordination would be to ensure the accountability of the information, create a single point of contact for information collection, create a standardize format and enforce specific timelines for collection.  This will ensure all parties involved own their information and allow for planning and preparation of the information prior to submission.