Developing quality attributes

Once the architecture decisions are made, the next step is to make that decision ready for the teams to implement. Pushing quality attributes to teams for development and compliance is a big challenge and is one of the most debated points in the Agile software development community.

There is no one-size-fits-all solution for this challenge; however, a combination of the following three approaches helps in overcoming this challenge:

• Technical backlog items: Some of the quality attributes need specific work from the team, such as developing a replication solution for the database or building the high availability of microservices. Such scenarios are converted and captured as user stories.
• Backlog constraints: In most cases, once the base solution is available, such as high availability or a shared data cache for faster customer access, several other user stories need to comply with the solution. In those cases, constraints such as acceptance...