Why Projects Fail

In the Article “Gaining Visibility and Commitment on Technology Projects” by Douglas M. Arnstein, he explains the proper procedures for a successful project outcome.  Developing a plan, with designated milestones and objectives, projected costs, resources, established core members, and stakeholder participation, ensures project success.  Mr. Arnstein further emphasizes that communication is the key to success, and while a project manager directs the project, it is the collective effort of more than one person that completes a project.

A project can fail due to many different reasons, but the following are key factors in project failure:

• Poor planning - failure to utilize established project management tools to properly produce a plan and unrealistic deadlines or tasks.

• Little or no documentation - improper documentation outlining a project, leads to a project that cannot be tracked, no milestones or completion identifiers, and no set goals.  A project needs documentation for direction.

• Bad communication – communication is the key to a successful project.  Communication must be maintained throughout all aspects from start to finish.  It helps establish the course of the project, to ensure it will be completed on time, or if adjustments are needed.

• Not enough, or no initial input from all resources involved - someone might have a good idea and start a project without prior consultation of the resources involved for completion.  Without this knowledge there may be a technical or financial limitation preventing its completion.  The more outsourcing that a project requires adds to the risk of failure and higher project cost.

• Improper resources – If all aspects of required resources are not explored during the planning phase, it may eventually be discovered that a project does not have the resources for completion.

• Lack of technical expertise – Especially in IT projects, improper communication might lead to project planners assuming that their technical resource has a capability that they do not possess.  IT representatives should always be included as a core member of an IT project.

• Unforeseen delays – While not every conceivable problem can be foreseen, all projects should include some type of buffer zone to absorb any unpredicted delays.  This will allow a project to remain on schedule as much as possible.  Projects should be flexible to account for delays.

• Changes to the project – The project scope should be clearly defined and documented.  Any changes that may arise should be vetted through a designated process to avoid the scope of the project changing after implementation.

In conclusion, projects that are unstructured, lack direction, and utilized little to no communication are doomed to fail.

Brad as a Project

     Looking at it from a project management perspective, a college student could be considered a “project” to manage.  Using that train of thought, lets look at how my life as a college student might progress for CS 250 IT Project Management.

     The project would begin by attending the first day of class, receiving the syllabus to establish milestones (projects due), and meeting my classmates.  The syllabus establishes the timeline of the project, and designated meeting times twice per week. 

The following goals should be met during the timeframe:

• Attend each class (allot “buffer” zone of two classes missed due to weather, etc.)
• Complete each assignment in a timely manner (before due date)
• Read the prescribed chapters, articles, etc.
• Communicate with fellow students (establish a communication/collaboration method for networking during project assignments)
• Schedule out of class meetings (if necessary)
• Routinely communicate with the Professor throughout the project about projects, assignments, etc.
• When put in a group environment, establish roles for each of the group members, switch roles when possible to encourage learning all aspects of project management
• For actual clients, routine contact will ensure the project is on track and the client’s goals are met
• Utilize Microsoft Project 2010 software to monitor project from start to finish
• Take good notes in class to gain information not provided by textbook or provided materials
• Ensure to ask questions to clarify information
• Keep a Positive Mental Attitude to ensure success
• Project completion is measured as all assignments, projects, exams complete by end of Semester

     Outside of CS 250, there are many external aspects that can affect the success of the project.  Since I commute from Janesville to Madison each day, vehicle operation, gas prices, road conditions, and weather are some of the obvious ones.  Having two vehicles reduces the risk factor of not being able to make it to class.  Living out of Madison also limits any out-of-class meetings with group members or clients.  However, proper planning or technology can substitute face-to-face meetings, via video conferencing, etc..  At present time, this project has a low risk factor rating of failure, as contingencies have been established for almost any problem.