Project Scope Creep
I once worked on a project, where the scope creep was an ongoing problem lurking around the corner. The initial scope for the project consisted of creating educational webinars that inform the group members about mentoring opportunities and scholarship program qualifications. Then as time went on, the discussion from the stakeholders became more about adding videos of the mentors to be included in the newly added virtual classrooms.
The client in this scenario gives many requests for additions to be added to the original project plan, which was to create webinars. While the project did have a budget that could absorb the duties that were being added the project, the timeline didn't change. The project manager was constantly giving deadline reminders to use at weekly meetings and emails. The extra requests were addressed by the stakeholders and Scope of Change documents were signed off on, but remained the timeline remained the same. The client was animate that July 5th was the live date and wouldn't bend on this date, though we only had nine months to create, change or rewrite the entire project.
I wished that the project leader wasn't such a pushover and was regarded as a friend of the team. But instead, the P.M was overpromising to the client and stakeholders, and under delivering on quality. In the end, the client wasn't concerned much with the lack of deliverables as much as he was excited about meeting the deadline that never moved. If the PM would have not agreed to so many additions that weren't going to get timeline consideration, then the project would have been much simpler.
