Where are high-level project requirements captured in Agile?

High-level project requirements in Agile are captured in the Product Backlog. The Product Backlog serves as the single source of truth for all work needed on the project, listing features, enhancements, bug fixes, and any other requirements. It is a dynamic and evolving document that is continually refined throughout the project lifecycle, ensuring that the most valuable items are prioritized and addressed during sprints.

This approach allows for flexibility and adaptation, accommodating changes in requirements as the project progresses and stakeholders gain more clarity or as market conditions shift. High-level requirements are typically presented as user stories within the Product Backlog, enabling the team to understand the needs and goals of the end-users or customers.

Options like the Sprint Backlog focus specifically on tasks and work planned for the current sprint, while a project charter is generally used in more traditional project management methodologies and captures broader project context and goals rather than granular requirements. A traditional requirements document does not align with Agile principles, which emphasize iterative development and flexibility rather than extensive upfront documentation.