A key area you are missing is Technical Excellence as described by the LeSS framework.
- Specification by Example
- Thinking about testing
- Continuous integration
- Continuous delivery
- Architecture & design
- Clean Code
- Acceptance testing
- Test automation
- Test-Driven development
These might sound like development practises and some are, still I think the lead quality person in an Agile organisation should closely relate to them, as:
Organizational Agility is constrained by Technical Agility
Read more: https://less.works/less/technical-excellence/index.html
This is important because:
UncleBob first presents, the secondary value (which most people believe is
the most important and valuable) as: ‘The secondary value of the
software is its behavior”. He explains that the primary value is more
subtle, and really it is more important than the behavior. And
presents the primary value as The software’s ability to tolerate and
facilitate such ongoing change to accommodate for the evolving
customer requirements. This means that, the main value of the software
is that it is soft.
Read more: https://medium.com/@mvidaurre/what-is-the-value-of-software-development-c90ac18b786d
I think this also related to the three aspects of software quality, namely: Functional, Structural and Process. The Quality Architect (A title I don't like) should focus on the quality of these three areas.
In Agile you want your organisation to not resists change, nor should your product. If it does you bring down process and functional quality.