Book Image

Becoming an Agile Software Architect

By : Rajesh R V
Book Image

Becoming an Agile Software Architect

By: Rajesh R V

Overview of this book

Many organizations have embraced Agile methodologies to transform their ability to rapidly respond to constantly changing customer demands. However, in this melee, many enterprises often neglect to invest in architects by presuming architecture is not an intrinsic element of Agile software development. Since the role of an architect is not pre-defined in Agile, many organizations struggle to position architects, often resulting in friction with other roles or a failure to provide a clear learning path for architects to be productive. This book guides architects and organizations through new Agile ways of incrementally developing the architecture for delivering an uninterrupted, continuous flow of values that meets customer needs. You'll explore various aspects of Agile architecture and how it differs from traditional architecture. The book later covers Agile architects' responsibilities and how architects can add significant value by positioning themselves appropriately in the Agile flow of work. Through examples, you'll also learn concepts such as architectural decision backlog,the last responsible moment, value delivery, architecting for change, DevOps, and evolutionary collaboration. By the end of this Agile book, you'll be able to operate as an architect in Agile development initiatives and successfully architect reliable software systems.
Table of Contents (19 chapters)
1
Section 1: Understanding Architecture in the Agile World
Free Chapter
2
Chapter 1: Looking through the Agile Architect's Lens
4
Section 2: Transformation of Architect Roles in Agile
8
Section 3: Essential Knowledge to Become a Successful Agile Architect
15
Section 4: Personality Traits and Organizational Influence

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...