Causes for IT Project Failure, II
Part 2 in a 3-part series
Goals and Objectives:
Staff members involved in IT projects often complain about unclear goals and objectives. In projects like software rollouts, project managers must develop and communicate clear objectives, while also minding the number of goals the projects might have. Although goals are a good thing, too many may ultimately confuse and distract a staff from the project at hand. It is also important to limit unexpected changes in user expectations and requirements as a project progresses. Changing expectations without clear communication will no doubt dissatisfy your customer, frustrate your employees, and add unnecessary costs.
Time estimates:
Time is of the essence – especially for project managers. When planning a project, a well calculated time frame is imperative to an accurate budget. Project managers make the common mistake of assuming the total time needed for a project’s completion is equal to the time on task. However, this does not account for interruptions. Project managers need to focus on the total duration of time needed (which includes interruptions), rather than the time on task.
More to come in the next and final post on this topic… in the meantime, BigWave can help eliminate many of the causes of IT project failure. Contact BigWave today for more information.
Written by John Livermore - Multi-site Project Management
Email This Post