Project Scope Control Management
From apppm
(Difference between revisions)
(→Abstract) |
|||
| Line 1: | Line 1: | ||
==Abstract== | ==Abstract== | ||
| − | + | In an ideal world, once a scope has been defined and moved into prototyping and construction, no changes will be made to the requirements or the extent, but in reality, project scope is continuously evolving over the entire lifecycle of the project. Therefore, it is significantly important that the scope identifies all the work that the project will accomplish to achieve its final goal and have a clear and easy scope management process that refers to the set of various processes that ensure a project's scope is accurately defined and mapped. <ref name = "besefi">Project Management Institute (2013). ''A Guide to the Project Management Body of Knowledge (PMBOK® Guide) 5th edition''. Page 105</ref>. | |
| − | + | ||
==Introduction== | ==Introduction== | ||
Revision as of 18:13, 17 February 2019
Contents |
Abstract
In an ideal world, once a scope has been defined and moved into prototyping and construction, no changes will be made to the requirements or the extent, but in reality, project scope is continuously evolving over the entire lifecycle of the project. Therefore, it is significantly important that the scope identifies all the work that the project will accomplish to achieve its final goal and have a clear and easy scope management process that refers to the set of various processes that ensure a project's scope is accurately defined and mapped. [1].
Introduction
Application
Limitations
Glossary
References
- ↑ Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) 5th edition. Page 105
