Project Scope Management

Revision as of 14:17, 21 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]

Plan Scope Management

The first process according to the PMBOK is to create a scope management plan. The plan would record how the project scope would be defined, validated and controlled. ^[1] The scope management plan locks down the roles and responsibilities of persons involved in managing the project scope and is therefore a guide aimed at managing and controlling the scope. ^[4] To start developing the scope management plan and specifying of the project scope, one has to start examining the project charter

Collect Requirements

Define Scope

Create Work Breakdown Structure

Validate Scope

Control Scope

Conclusion

Annotated Bibliography

Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide) 5th edition: This book delivers a good understanding on the art of project scope management.

Mark Piscopo (2013). Scope Management Plan Template: The article breaks down the scope management plan. The article uses examples in every step it takes making it a good article to improve your knowledge of how the scope plan management is used in real life.

References

1. ↑ ^{1.0 1.1 1.2 1.3} Project Management Institute (2013). A Guide to the Project Management Body of Knowledge (PMBOK® guide) 5th edition. Newtown Square, Pennsylvania: Project Management Institute, Inc
2. ↑ Project scope. (et. al). Retrieved 10. February 2018 from http://searchcio.techtarget.com/definition/project-scope
3. ↑ Product Scope vs. Project Scope. (et. al). Retrieved 10. February 2018 from https://www.villanovau.com/resources/project-management/product-scope-vs-projectscope/#.WoAY7ud0ZEY
4. ↑ Mark Piscopo. (et. al). Scope Management Plan Template. Retrieved 12. February 2018 from http://www.projectmanagementdocs.com/project-planning-templates/scope-management-plan.html