An aviation software project has been structured to use agile methods, but industry regulations require detailed tracking and archival of product changes. What should the project manager reference to understand compliance impacts on the project?

The product backlog contains all desired features and requirements, including those driven by regulatory compliance. The Definition of Done (DoD) specifies the criteria that must be met for a product increment to be considered complete, often incorporating quality standards and regulatory requirements. Therefore, these two artifacts are crucial for understanding and ensuring compliance impacts are addressed throughout the project. User stories and the release plan describe functionality and delivery timelines, but don't explicitly detail compliance criteria. The scope of work is a high-level document and the product backlog is more detailed for agile. A sprint retrospective is a process improvement meeting, not a source of compliance requirements.