In SAFe, who is responsible for accepting user stories as done?

In SAFe, the responsibility for accepting user stories as done lies with the Product Owner. This role is pivotal in defining what 'done' means for each user story and ensuring that all acceptance criteria are met. The Product Owner collaborates closely with the development team to clarify requirements and provides input on the product's direction.

Acceptance by the Product Owner ensures that the completed work aligns with customer needs and business goals. This role plays a critical part in maximizing the product's value by making informed decisions about prioritization and acceptance of features and functionalities. By holding this responsibility, the Product Owner helps maintain a clear focus on delivering high-quality results that satisfy stakeholders and end users.

While other roles, such as the Scrum Master and the project manager, may support the process in various ways, they do not have the authority over the acceptance of user stories like the Product Owner does. The entire team does contribute to the development and delivery of the work, but the final acceptance decision rests on the Product Owner to ensure alignment with the overall vision and user expectations.