In Agile and Adaptive environments, as described in the PMBOKGuide and the Agile Practice Guide, requirements are not captured in a static scope statement but are managed dynamically through a Backlog.
* Backlog (Choice D): In Agile, the Product Backlog is the primary document (an ordered list) representing the project scope. It consists of user stories, features, or requirements that need to be addressed. Requirements are " refined " and prioritized within this backlog throughout the project, rather than being finalized upfront. This aligns with the Agile principle of " responding to change over following a plan. "
* Sprint (Choice B): A Sprint is a time-boxed iteration (typically 1-4 weeks) during which a specific set of work is completed. While requirements from the backlog are selected for a Sprint Backlog, the Sprint itself is a container for work, not a definition of the requirements themselves.
* Charter (Choice C): The Project Charter (or Agile Charter) is a high-level document that authorizes the project. While it may contain a high-level vision and objectives, it does not define the detailed requirements that evolve during the project.
* Metrics (Choice A): These are measurements (such as velocity or cycle time) used to track progress and quality, but they do not define the functional or non-functional requirements of the product.
In scope management for adaptive lifecycles, the Product Backlog serves as the evolving " single source of truth " for what the team needs to build, ensuring that the most valuable requirements are always addressed first.