Avoiding the Most Common Mistakes when Managing IT Projects (Part 1)
As IT providers, we are always looking for ways to better manage projects. Since so many of us are often juggling multiple technical projects at one time, I thought it would be helpful to provide a few examples of common mistakes to avoid when managing these projects, as well as solutions. Speaking from experience, avoiding these challenges will make you better at managing successful IT projects.
Over the next two blogs, I have seven mistakes (and solutions) to share. Here are the first four:
Mistake # 1: Not choosing the right project team
Allocating human resources to a project begins with the Project Manager. The Project Manager is experienced in the technology and is responsible for identifying potential issues and minimizing mistakes.
Assembling the team that will execute the project tasks is just as critical to project success. Understanding the technical competencies of each individual and how they may be best utilized in the project decreases the chance of mistakes.
Use staff that are qualified or experienced for the tasks needed for the project. Engaging a network engineer or helpdesk professional who does not have in-depth experience with the network and business operation can cause your project to go over budget. Worse, your users are likely to lose confidence in your team when there are too many follow-up issues at the conclusion of the project.
Additionally, where possible, have at least one person on the project team who will be an end-user of the final product. This team member can help identify issues with the way the new system will be used before it goes into production.
Mistake # 2: Poor planning or planning without goals
Any time a project is completed without a plan, it is destined to fail to meet someone’s expectations. Conduct a requirements analysis with all affected departments in an organization to determine clear and specific goals. This will ultimately ensure that the designed solution meets the needs of the entire organization.
Sticking to goals once decided is important as well. When designing a solution, a Project Manager must have the ability to question or reject a request, especially if it will have a severe impact on the success of the project. A minor request from the client’s perspective may have a major impact on the project team’s ability to achieve goals.
Additionally, all project plans should include testing at various milestones throughout the project. This will ensure the project is being completed according to the plan, and will help you adjust the plan as needed. Testing throughout the project will avoid pitfalls.
All project plans should also include steps to train the end-user, as even the smallest network changes require modifications to human workflow. If the staff is not trained, the organization will not capture the full value of the project. When at all possible, provide end user documentation and quick reference guides.
Mistake # 3: Not implementing or following standards and procedures
Although each project is as unique as the network environment in which it is being implemented, there are always practice standards and procedures to be followed. The procedures should be repeatable for all similar projects, and the project team must be careful not to stray from them. IT professionals are often curious and experiment with technology, but a project is not the time to experiment. The entire team must stick with the plan as managed by the Project Manager.
Mistake # 4: Upgrading just for the sake of upgrading
Successful Project Managers should only plan and implement projects that meet the current and future goals of the organization. While this one sounds obvious, IT projects should be planned primarily around business needs and not necessarily by the latest-release calendar of a hardware or software manufacturer.
