Summary

Even though the architect role is not standard, like Product Owner and Scrum Master in agile development, it is still critical for many essential activities. However, it is the architect's responsibility to showcase their work's value in a transparent way, such as by using business language for selling architecture ideas.

In this chapter, we have learned that one of the key objectives of agile software development is to satisfy customers' needs early and frequently. The purist view of demand-based pull systems often challenges architecture activities. However, robust evolutionary architecture is important for delivering quality solutions with a sustainable flow in reality.

Then, we learned about the importance of architects demonstrating value and useful techniques. Architecture in agile needs rigor and work transparency, and must manifest value. Using shared product backlogs and linking technical and business backlogs help architects sell their work. Determining...