This weekly upload is going to be a study blog, written to help me revise my course, Project Management BSc. Hopefully, it will also create a good overview for anyone else looking to study the same thing.
According to the APMBoK 6th edition, “Scope comprises the totality of the outputs, outcomes and benefits and the work required to produce them”. Simply put, the scope is the entirety of a project, from the beginning to the end of project, what it comprises of and the benefits realised after its completion.
Scope management is the process that is used to control the outputs and outcomes and identify the benefits. “Scope management is the process whereby outputs, outcomes and benefits are identified, defined and controlled (APMBoK 6th)”
Without scope management, a project is at risk of scope creep, whereby the project exceeds its intended criteria and therefore increasing in cost, time, disputes, quality, etc. and can ultimately cause the project to fail.
There are 6 steps to defining a project:
- Requirement management – this involves assessing, capturing and documenting the needs and objectives that are required by the stakeholders.
- Defining the project scope – to do this you need to confirm the key aspects of the project, such as, project objectives, deliverables, milestones, technical requirements, limits and exclusions and reviews with customer.
- Determining the Priorities – essentially you will need to establish what areas within the project are critical and which can be compromised if necessary. E.G. time, cost or quality. These priorities should be made clear within the development phase but can change throughout the life cycle.
- Create a Work Breakdown Structure – a WBS is a hierarchical outline (map) that identifies the work elements involved in a project. This is a helpful way to plan a project because you can use it to break down the scope. It also helps manage plan, schedule, and budget as well as defines communication channels and assists in coordinating the various project elements.The lowest level in the WBS is the work packages.
- Integrating the WBS with the Organisation – You can use an Organisational Breakdown Structure (OBS) to do this. An OBS shows how an organisation is going to manage its work responsibility within the project.
- Coding the WBS for the Information System – this highlights the levels and organisational levels of the WBS, it’s work packages, and budget and cost elements.
The Responsibility Matrix
Using the WBS and OBS you can construct a Responsibility Matrix, RAM. A RAM is used to allocate the work packages to people, organisations or 3rd parties. A RAM can include information such as who is responsible, should be consulted or informed about certain tasks.
Thank you to the continued support on this blog series 🙂