Two Major Reasons Why a Project is Late

Employee turnover refers to a ratio comparison of the number of members that “must be” replaced or left in a given time period to the average number of total members in the team. This raises questions such as “What happens if they leave?”, “How dependent is our schedule on people with these exact skills?”, “Will information be lost with the person?” and “How can we keep them / replace them?”

Huge consideration is given to this idea since it is seen to not only increase cost and expenses but also making a project late. Why? Simply because, if a member left during or halfway through developing a project it will certainly incapacitate the team. Before making a project, the job is divided equally thus if one member will leave it will leave a gap or additional job to another member. This problem also relates to employing another person to balance the tasks again but then we already know (from our Activity 1) that getting a new person to do a project has it own disadvantages and also makes a project late, especially, if that person isn’t familiar with the project at hand. Therefore, employee turnover and the supposedly “solutions” to it creates problems and tends a project to be late.

Changing of requirements or requirements volatility or instability results to certain complications that can really make a project late and even fail. The instability of requirements can be fine if its only changes minor details of the project. Minor adjustments or simple solutions can be enough but then these cannot be if major details are to be changed. It can result to certain degrees of changes such as from changing a whole task, or adding a new task, or having one or more section rendered useless by this new development and the worst of which is to have to do the project again from the top. Sometimes when certain project requirements change it tends to delay, or use up a lot of time in adjusting and mending the project.

New paths and strategies that weren’t considered at the first might be taken and used now thus making study and testing time longer which can lead to making the project late or fail. It can be analogous to cooking, if we cook a dish faster if we stick up to its traditional ingredients but if we were going to use other untraditional ingredients we have to taste and test it before putting it to the pot to be sure that the taste will be the same. Certain details such as the heating the pot more or simmering ingredients linger or shorter can be implemented when such recipe change is done. So it is with requirements volatility or instability.