Which activity is NOT part of maintaining architectural compliance in SAFe?

Maintaining architectural compliance in SAFe involves a structured approach to ensure that the architecture adheres to established standards, aligns with business objectives, and is regularly reviewed by relevant stakeholders.

Incorporating standards into design is a crucial activity because it ensures that all architectural designs comply with predefined guidelines, which supports consistency and quality across the product or solution being developed. Regularly reviewing architecture with stakeholders is essential for capturing feedback, making necessary adjustments, and ensuring that the architecture remains relevant to current and future needs. Aligning architecture with business goals is fundamental, as it ensures that the architectural framework supports the organization's objectives, enabling successful delivery of value to customers.

Delegating governance to the development team deviates from the principle of maintaining architectural compliance. While development teams play a key role in implementing the architecture, governance must involve higher-level oversight to ensure adherence to strategic objectives, standards, and compliance requirements. Governance ensures that decisions made by development teams align with the overall architectural vision and maintain compliance throughout the development process. Therefore, this option does not fit within the framework of maintaining architectural compliance in SAFe.