### 6.3.3 Architecture Owner (ArOw) The Architecture Owner (ArOw) is the **solution architect responsible for the Agile Project Core Team’s (A- PCT) architecture decisions**. The Architecture Owner **facilitates** the creation and evolution of the **overall solution design** and **considers existing or planned investments** made in other information systems/components. Because architecture **can generate critical project risks**, one must ensure the team mitigates those risks. Although the Architecture Owner is **typically the senior developer** on the team (sometimes also referred to as the technical architect, software architect, or solution architect), it is **not a hierarchical position** to which other team members report. The Architecture Owner should have a **strong technical background** and a thorough understanding of the business domain and he/she is **expected to sign off and deliver work like any other team member**. **Responsibilities** - **Guides** the creation and evolution of the architecture of the information system. - **Favours a collaborative, team-based approach** while ==avoiding dictating the architectural direction==. - **Conducts the technical discussions** but ==is not solely responsible for the architecture==. - **Leads the initial architecture envisioning** effort at the beginning of the project and supports the initial requirements envisioning effort (particularly when it comes to understanding and evolving the non-functional requirements for the information system), **focusing** on the project lifecycle and also **on the evolution and maintainability of the information system**. - Ensures the **alignment** of the architecture of the information system with the guidelines and recommendations of the **Architecture Office (AO)** and the support of the established **enterprise architecture principles**. - **Leverages existing and/or planned IT investments** in the organisation by continuously promoting a **culture of reuse and interoperability** within the Agile Project Core Team (A-PCT). - Contributes to the organisation’s set of **reusable IT assets** by considering the overall domain which the information system will support and the overall IT strategy. - **Informs the Team Coordinator (TeCo) and the Project Manager (PM) of the main architectural risks** and contributes to defining a suitable risk management strategy.