click below
click below
Normal Size Small Size show me how
APMP Section 6
Scope management
Term | Definition |
---|---|
Breakdown structure | A hierarchical structure by which project elements are broken down, or decomposed. |
Deliverable | A product, set of products or package of work that will be delivered to, and formally accepted by, a stakeholder. |
Product | A tangible or intangible component of a project’s output. Synonymous with deliverable. |
Scope management | The process whereby outputs, outcomes and benefits are identified, defined and controlled. |
Work package | A group of related activities that are defined at the same level within a work breakdown structure. |
Acceptance criteria | The requirements and essential conditions that have to be achieved before a deliverable is accepted. |
Requirements management | The process of capturing, assessing and justifying stakeholders’ wants and needs. |
Users | The group of people who are intended to benefit from the project or operate the deliverables. |
Change control | The process through which all requests to change the baseline scope of a project, programme or portfolio are captured, evaluated and then approved, rejected or deferred. |
Change freeze | A point after which no further changes to scope will be considered. |
Change register | A record of all proposed changes to scope. |
Configuration management | The administrative activities concerned with the creation, maintenance, controlled change and quality control of the scope of work. |
Scope | The totality of the outputs, outcomes and benefits and the work required to produce them. |
Configuration | Functional and physical characteristics of a product as defined in its specification. |