Why is project scope management so challenging in IT projects? What suggestions do you have for preventing scope creep in projects? What did you think about the approach Northwest Airlines used for improving user input and reducing scope changes on their reservation system project?

Explanation:

Ways to Avoid Scope Creep

Scope creep is what happens when changes are made to the scope of a project without any control. Changes happen to projects all the time without been notify ontime as a project manager. It is that very rare project that ends up delivering exactly what was asked for on the first day. However, without there being some control over the changes, a project manager has little chance of keeping on top of the work and managing the project effectively.

Generally, scope creep is when new requirements are added after the project has commence. These changes are not properly reviewed. The project team is expected to deliver them with the same resources and in the same time as the original scope.

On the other hand, as a project manager you could end up with a project with lots of approved, considered changes, that never ends because every time you think you have finished a new requirement arrives in your inbox and you have to make more changes.

The following are five ways to keep control of your project.

1-Document the Requirements

2-Set up Change Control Processes

3-Create a Clear Project Schedule

4-Verify the Scope with the Stakeholders

5-Engage the Project Team

that without the operating systems you would have to control and synchronize computer hardware.