Misplaced Pages

This is the current revision of this page, as edited by MrOllie (talk | contribs) at 00:16, 22 February 2024 (Reverted 1 edit by Paverotti (talk): Unreliable source / citespam). The present address (URL) is a permanent link to this version.

In project management, scope is the defined features and functions of a product, or the scope of work needed to finish a project. Scope involves getting information required to start a project, including the features the product needs to meet its stakeholders' requirements.

Project scope is oriented towards the work required and methods needed, while product scope is more oriented toward functional requirements. If requirements are not completely defined and described and if there is no effective change control in a project, scope or requirement creep may ensue.

Scope management is the process of defining, and managing the scope of a project to ensure that it stays on track, within budget, and meets the expectations of stakeholders.

See also

• Cost overrun
• Requirements management
• Scope statement

References

1. "Project Management Scope". Project Management Skills. Retrieved 2021-11-24.
2. Luiz Lampa, I.; de Godoi Contessoto, A.; Rici Amorim, A.; Francisco Donegá Zafalon, G.; Valêncio, C. and Souza, R. (2017). Project Scope Management: A Strategy Oriented to the Requirements Engineering. In Proceedings of the 19th International Conference on Enterprise Information Systems - Volume 2: ICEIS, ISBN 978-989-758-248-6; ISSN 2184-4992, pages 370-378. doi:10.5220/0006318603700378
3. ^ Sanghera 2019.
4. Haworth, Suzanna (2021-09-14). "Project Scope Creep: What It Is And 5 Core Ways To Manage It". The Digital Project Manager. Retrieved 2021-11-24.
5. Kerzner 2009.

Bibliography

• Kerzner, Harold (2009). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (10th ed.). Wiley. ISBN 978-0-470-27870-3.
• Sanghera, Paul (2019). PMP in Depth (Third ed.). Apress. doi:10.1007/978-1-4842-3910-0. ISBN 978-1-4842-3910-0.

• Project management