This article focuses on two agile architecting methods that provide rapid feedback on the state of agile team support: architecture-centric risk factors for adoption of agile development at scale and incremental architecture evaluations.
In this paper, we present lessons we learned while working with a
large program, helping it to modernize its very large transaction-based system that
operates 24x7, while adopting agile software development. We focus on two agile
architecting methods we used that provide rapid feedback on the state of agile
team support: architecture-centric risk factors for adoption of agile development at
scale and incremental architecture evaluations. This article was first published in Crosstalk.