click below
click below
Normal Size Small Size show me how
Requirements mgmt
APM PMQ Competence 16 terminology
| Term | Definition |
|---|---|
| Baseline | The reference levels against which a project, programme or portfolio is monitored and controlled. |
| Configuration | The functional and physical characteristics of a product as defined in its specification. |
| Configuration item | A part of a configuration that has a set function and is designated for configuration management. It uniquely identifies all items within the configuration. |
| Configuration management | Encompasses the technical and administrative activities concerned with the creation, maintenance, controlled change and quality control of the scope of work. |
| MoSCoW | A quasi-acronym representing four options for a proposed requirement or system feature, being Must have, Should have, Could have and Won't have. |
| Requirements | The stakeholders’ wants and needs clearly defined with acceptance criteria. |
| Requirements management | The process of capturing, assessing and justifying stakeholders’ wants and needs. |
| Scope | The totality of the outputs, outcomes and benefits and the work required to produce them. |
| Scope management | The process whereby outputs, outcomes and benefits are identified, defined and controlled. |
| Acceptance criteria | The requirements and essential conditions that have to be achieved before a deliverable is accepted. |