What Figure 2 does not show is that many Product Management teams include business analysts (what DAD would consider a Specialist role) and Domain Experts. Agile business analysts will support Product Owners that find themselves working at scale, often assisting them when stakeholders are geographically distributed, in situations where the problem domain is complex and requires deep analysis, or in regulatory situations requiring greater levels of requirements documentation. Domain experts are often called in on an as-needed basis to help Product Owners to work through complex domain issues.
The Architecture Team
The purpose of the Architecture Team is to formulate an architectural strategy at the program or enterprise levels; to communicate that strategy to their customers (both IT and business stakeholders); to evolve the strategy over time based on their learnings working with development teams and other stakeholders, and to resolve any architecture-level technical issues (such as evolving interfaces or changing underlying technical infrastructure) that arise over time. This team is also sometimes called an Architecture Owner team, Agile Architecture team, or even Enterprise Architecture team. A more detailed description of the activities this team may choose to perform as captured by DAD’s Enterprise Architecture process blade.
Figure 3, similar to Figures 1 and 2 before, show how Architecture teams can be organized. You see that the team is led by a Chief Architecture Owner, sometimes called a Chief Architect or Chief Enterprise Architect. The Architecture Owners from each delivery team should be members of the Architecture Team, so that they can share their learnings with others, get help from their colleagues as needed, and negotiate changes to architectural aspects of the solutions that they are working on as their overall strategy evolves. The Chief Architecture Owner will often be an Architecture Owner on one or more delivery teams. As with the other leadership teams, the Architecture team will self organize. We’ve seen teams that meet once a week for an hour, some teams that meet bi-weekly, and some teams that meet monthly. It is common for Architecture Owners to request an ad-hoc meeting of all or a subset of the Architecture Team to discuss an architecture issue that has become critical for them.