On Scope Creep (again)

“What obstacles do project managers face to successful completion of an Information Technology project?”

Certified IT Professional: Healthcare group

“As others have notes in their answers, the biggest issue I've encountered as a Project Manager of a project to develop a dynamic mapping extension for a commercial software product was "scope creep." Without a detail Functional Specification developed with user input/client input at the beginning of the project you're constantly faced with requests to change widgets, colors, adding features & functionality. It takes a lot of time up front for the Functional Spec but it saves a lot of time, frustration, and confrontational communications as the project moves forward.

Be sure you understand the deployment environment -- e.g., SQL 2000 or SQL 2005, Internet Explorer/FireFox/Mac, etc. so the application is developed to work in the appropriate environments.

Also, good change control with tools such as Visual SourceSafe is highly recommended.
Finally, engage users, both sophisticated and non-sophisticated in product design.

MüTō Observation:

That veritable virus "scope creep"! I can't agree with you more. If its not fully controlled, a Project Manager will lose all direction when Scope Creep rears its ugly head.

If a project manager has an ability to communicate clearly, these obstacles become manageable.

If they can properly motivate their team, then issues about the environment are brought to their attention, and risks are raised earlier. If the project manager can hold his team-mates, suppliers, sponsors, and beneficiaries accountable, then issues surrounding requirements (scope creep), environments, technology, delivery of milestones, funding, etc... become less risky to the project's success.