Which of the following terms is used to refer to the documentation of requirements and project progression?

The term "requirements specification" is the most appropriate choice to describe the documentation of requirements and project progression. Requirements specification refers to a detailed description of the system's functionalities, features, and constraints as gathered from stakeholders. It serves as a formal agreement between stakeholders and the project team, outlining what needs to be delivered.

In terms of project progression, the requirements specification is critical as it guides the development process, ensuring that the project aligns with business needs and stakeholder expectations. It acts as a reference point throughout the project lifecycle and helps in tracking progress against the defined requirements. The clarity and structure provided by a well-prepared requirements specification help in managing changes and maintaining focus on project goals.

Meanwhile, other terms like project scope refer to the boundaries of a project, including the work required to generate deliverables, but do not specifically encapsulate detailed requirements. Stakeholder analysis focuses on identifying and assessing the needs and influence of stakeholders, while change requests pertain to alterations needed after requirements have been initially set. Therefore, while all these terms are relevant in project management, "requirements specification" is distinctly designed to document both requirements and the associated progression in a project.