Project Scope Management
(→Abstract) |
|||
| Line 1: | Line 1: | ||
==Abstract== | ==Abstract== | ||
| − | The basic concept of a project scope management is defining and controlling what is included and what is not included in the project. <ref name = "besefi">Project Management Institute (2013). ''A Guide to the Project Management Body of Knowledge (PMBOK® guide)''. Newtown Square, Pennsylvania: Project Management Institute, Inc </ref>. It is vital for a project manager to have a scope, it defines the step the needs to be taken in ordered to achieve the project goals. It includes, but is not limited to, what the end goal is, how much the whole project and every segment of it will cost, how much work it will take and when the project is supposed to be finished. <ref>http://searchcio.techtarget.com/definition/project-scope</ref> | + | The basic concept of a project scope management is defining and controlling what is included and what is not included in the project. <ref name = "besefi">Project Management Institute (2013). ''A Guide to the Project Management Body of Knowledge (PMBOK® guide)''. Newtown Square, Pennsylvania: Project Management Institute, Inc </ref>. It is vital for a project manager to have a scope, it defines the step the needs to be taken in ordered to achieve the project goals. It includes, but is not limited to, what the end goal is, how much the whole project and every segment of it will cost, how much work it will take and when the project is supposed to be finished. <ref>Project scope. (et. al). Retrived 10. February 2018 from http://searchcio.techtarget.com/definition/project-scope</ref> |
| − | The following processes are the main pillars of the Project Scope Management and whole chapters will be dedicated to each process in the following article. These processes are: Plan Scope Management, Collect Requirements, Define Scope, Create Work Breakdown Structure, Validate Scope and Control Scope. The processes all connect in some way. It is also important to mention that in the project framework, it is possible to define the scope in two different ways, one way is to refer to the scope as product scope and the other ways is called project scope. <ref name = "besefi"/> The product scope refers to how a product is made while a project scope would focus more on how to deliver the service or product. A product scope could therefore be included in the project scope. <ref>https://www.villanovau.com/resources/project-management/product-scope-vs-project-scope/#.WoAY7ud0ZEY </ref> The scope baseline is considered as a sacred plan and is not to be changed unless it follows formal change control procedures. It is therefore important for a project manager to have a scope and manage it properly. <ref name = "besefi"/> | + | The following processes are the main pillars of the Project Scope Management and whole chapters will be dedicated to each process in the following article. These processes are: Plan Scope Management, Collect Requirements, Define Scope, Create Work Breakdown Structure, Validate Scope and Control Scope. The processes all connect in some way. It is also important to mention that in the project framework, it is possible to define the scope in two different ways, one way is to refer to the scope as product scope and the other ways is called project scope. <ref name = "besefi"/> The product scope refers to how a product is made while a project scope would focus more on how to deliver the service or product. A product scope could therefore be included in the project scope. <ref>Product Scope vs. Project Scope. (et. al). Retrived 10. February 2018 from https://www.villanovau.com/resources/project-management/product-scope-vs-project-scope/#.WoAY7ud0ZEY </ref> The scope baseline is considered as a sacred plan and is not to be changed unless it follows formal change control procedures. It is therefore important for a project manager to have a scope and manage it properly. <ref name = "besefi"/> |
==Annotated Bibliography== | ==Annotated Bibliography== | ||
Revision as of 12:01, 11 February 2018
Abstract
The basic concept of a project scope management is defining and controlling what is included and what is not included in the project. [1]. It is vital for a project manager to have a scope, it defines the step the needs to be taken in ordered to achieve the project goals. It includes, but is not limited to, what the end goal is, how much the whole project and every segment of it will cost, how much work it will take and when the project is supposed to be finished. [2] The following processes are the main pillars of the Project Scope Management and whole chapters will be dedicated to each process in the following article. These processes are: Plan Scope Management, Collect Requirements, Define Scope, Create Work Breakdown Structure, Validate Scope and Control Scope. The processes all connect in some way. It is also important to mention that in the project framework, it is possible to define the scope in two different ways, one way is to refer to the scope as product scope and the other ways is called project scope. [1] The product scope refers to how a product is made while a project scope would focus more on how to deliver the service or product. A product scope could therefore be included in the project scope. [3] The scope baseline is considered as a sacred plan and is not to be changed unless it follows formal change control procedures. It is therefore important for a project manager to have a scope and manage it properly. [1]
Annotated Bibliography
Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide): This book delivers a good understanding on the art of project scope management.
References
- ↑ 1.0 1.1 1.2 Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide). Newtown Square, Pennsylvania: Project Management Institute, Inc
- ↑ Project scope. (et. al). Retrived 10. February 2018 from http://searchcio.techtarget.com/definition/project-scope
- ↑ Product Scope vs. Project Scope. (et. al). Retrived 10. February 2018 from https://www.villanovau.com/resources/project-management/product-scope-vs-project-scope/#.WoAY7ud0ZEY
