Seven Deadly Viruses That Can Infect Your Software Projects. How to Deal with Them. This guest post is by Utpal Vaishnav. Although we take the best precautions to protect our mobiles, computers and laptops from viruses, did you know that viruses can also infect the projects we manage? These viruses can cause serious project health problems, such as missed deadlines, unmanaged expectations, client-relationship issues, and sometimes even business disasters. Here are seven deadly viruses that can be fatal and how we can protect the projects we manage:

  • Improper engagement models This model has a major problem: Both parties are trying to achieve the exact opposite. While project sponsors want to see the project complete in the shortest time possible, offshore companies want to make more money. This is a classic example of a win-lose relationship. You must ensure that project management is?Project? Is the subject not an ‘hourly rate?
  • Poor requirement gathering: Many projects start with vague, high-level requirements. Developers may decide to build whatever they think is appropriate, without any knowledge of the client’s business. As a project manager, it is your responsibility to ensure that the requirements are precise, measurable, and exactly as the project sponsor requires.
  • Unrealistic deadlines: Many project sponsor manage projects through “pushing”. Developers are often given unrealistic deadlines. These pressures are too much for most developers, who tend to focus on the numbers at the expense of quality. The result is a disastrous end-product. You must ensure that developers have enough time to complete the tasks as a project manager. You must be proactive and convince project sponsors to set realistic deadlines.
  • Feature-creep is uncontrolled change in project scope. It is the addition of new features to a project without any corresponding budget, schedule, or resources increases. This feature-creep can lead to project-overruns. As a project manager, it is important to ensure that there is strict change control and that any change in scope is accompanied by a change in budget, schedule, or resources.
  • Poor or insufficient testing: Many projects don’t have the freedom to go through all stages of SDLC. Sometimes project stakeholders don’t pay enough attention to the importance of requirements gathering and testing. You, as a project manager, need to ensure that:

  • Requirements can be frozen so that measurable test plans are possible to be created and acted on.
  • It is important to allocate sufficient time for unit testing, integration testing, and most importantly user acceptance testing.
  • Testers are trained so that they understand the purpose of testing the application and can make it bug-free.
  • Ineffective communication: Ineffective communication may lead to frustrations and surprises. This can lead to a demotivated team. The project is in chaos. You as a project manager must ensure that the communication plan meets the basic function of communication. This is the coordination of actions. It is important to clearly state who will speak with whom and what type of actions.
  • Inferior Leadership: Project Without Leade