In project management fast moving schedules may at times be necessary, its technique employed to save time, fast moving schedules entail doing several things at once which necessitates re-arranging of tasks (Schiff, J. 2012). In the project fast moving schedule was a problem because it called for re-planning of the tasks and also brought in an avenue for disorganization. Fast moving schedules are hard to manage due to the concurrent nature of activities and this was one of the contributing factors to the distress of this project. It resulted to a generation of other problems.
The other problem that faced the project was early misunderstandings due to requirements. This problem arose due to lack of clearly spelt goals of what the outside software developer was required to do. The software developer lacked guided requirement to focus on leading to poor performance, this is one of the problems that set the project on the wrong foot from the word go (Top 10 Project Management challenges, 2013)
Another major problem that faced the project is management changes in the middle. This resulted in destabilization of the project; it interfered with progress of the project as scheduled. The new manager had to take time to settle, more time for project completion was wasted as the manager took more of it to familiarize with the project, the project details and blend in with the different people involved. The manager being new lacked the familiarity regarding the goals of the project, the purpose and duty of the staff and the exact role o outside software of developer. Unreliable performances towards deadlines are a challenge that the project faced. This came in form of poor quality work in the different critical milestones. The outcomes were unsatisfactory and this called for more time to rectify the performance and bring it up to par.
When the time for releasing the code for final QA before the release, the company discovered that the system functionality was not what they wanted, the outside software developer did not meet requirements in making of the software code. This problem stemmed from lack of effective communication. Lack of communication between all those involved in the project is one recipe for failure. The problem according to James clear (2011) could also result from the client not really being aware of what they or the contractor failing to understand what is required of them.
The time factor required fast action on the project progress and this forced the company to testing of the first release. This on another hand required the outside software developer to assist the in-team, this was a problem too because this was not what was initially agreed. According to Gasco Luo (2009), the spontaneous requirement that come in during project duration poses a challenge to stakeholders. This challenge commonly referred to as scope creep affected the outside software developer resulting in disagreements. More to that, the fast turnaround that was required of both teams to test and work on any remaining bugs worked to pile pressure on them.
Lastly the discovery of the bug that could result in problems during customer usage was another problem; it caused panic in the whole team and exposed lack of clearly spelt contingency plans. There was also the issue of the unresolved political considerations resulting in delay. By the time the vendor acted the deadline was very close. According to an article, “The Top Project Management Challenges” sometimes project calls for changes, when these changes are not well managed it can result to the problems in the project progress.
Most of the problems that affected the project could have been avoided if the manager had been keen. If I was the manager I could have ensured that the planning process was taken with due seriousness. The problem of fast moving schedule could have been avoided by proper planning and adequate allocation of time to avoid unnecessary rush (Kendrick, T., 2011)
Regarding the problem of misunderstandings due to requirements, I could have avoided the situation by informing the outside software developer of what exactly was required of them. Concerning the problem of unreliable performances to deadline, as the manager I could have avoided it by assigning of individual assignment to the different team members. This would have ensured diligence and accountability as each would have been responsible for their part. (Kendrick, T. 2011)
As the manager I could have moved to avert the problems by ensuring timely testing to ensure timely detection of any defects in the project. This would have prevented the delivery of the defective system and the late crisis that occurred.
Project management is a delicate issue that needs proper prior planning to ensure success. A project manager is supposed to be skillful and well equipped to run the project effectively because success of any project largely depends on the manager.
References
Cross V. (2013) Team work in a project, Texas: Hearst Communications, Inc retrieved from < http://smallbusiness.chron.com/teamwork-project-20957.html>
James, C. (2011) 7 Common Project Management Problems (And How to Solve Them),six revisions. Retrieved from< http://sixrevisions.com/project-management/7-common-project-management-problems-and-how-to-solve-them/>
Kendrick, T. (2011) 101 project management problems and how to solve them practical advice for handling real-world project challenges, New York: AMACOM, American Management.
Ofori, D. (2006) Problems of project management, Accra: Ghana University press
Schiff, J. (2012)12 Common Project Management Mistakes--and How to Avoid Them, retrieved from <http://www.cio.com/article/717321/12_Common_Project_Management_Mistakes_and_How_to_Avoid_Them>
