CAPM Practice: Explain the components of an adaptive plan

The product backlog is a living document — it evolves throughout the project as the team learns, stakeholders provide feedback, and the business context changes. Items are continuously added, removed, refined, re-estimated, and re-prioritized. This continuous evolution is a feature, not a bug: it ensures the team always works on the most valuable, relevant items based on current knowledge.

**Why not B:** Requiring complete detail before any sprint begins is a predictive (waterfall) approach, not adaptive. In adaptive projects, detailed requirements emerge progressively through iteration and feedback. Attempting to fully specify everything upfront wastes effort on items that may never be built or that will change.

**Why not C:** The product owner — not the development team — owns the product backlog and is responsible for prioritization based on business value. While the development team provides input on effort and technical considerations, prioritization by business value is a product owner responsibility.

**Why not D:** Locking the backlog after the first sprint would eliminate the team's ability to respond to change, which is the core advantage of adaptive approaches. New learning, stakeholder feedback, and market changes must be reflected in the backlog throughout the project.