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

Documenting software architecture

Architecture documentation refers to recording guidelines, practices, architecture intents, decisions, rule books, reference architectures, and patterns using various tools such as wiki-style documentation tools, modeling tools, and Agile team tools. This section elaborates on this idea.

Different proposals for documenting architecture

Architecture documentation evolved over the years from rigid template-based documentation to an essential information-based approach. While many of those legacy ideas proposed by traditional frameworks such as Rational Unified Process (RUP) are still valid in Agile software development, the ways of documenting and the depth of documenting are different.

View-centric approaches were popular in the early 2000s. The essence of architectural viewpoints is that different stakeholders want to see different architectural views based on their interests. The different view frameworks are as follows:

  • The 4 +1...