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

In this chapter, we have learned the importance of documentation in developing software systems following Agile development methodologies. We have learned the reasons for documentation, why documentation is considered a flow barrier, and some of the challenges associated with traditional documentation methods, such as exceeded budget, no one reading the documentation, the fact that it is a waste of effort, change tolerance, and documentation silos.

Furthermore, we have explored the Lean-Agile documentation and the adoption of evolutionary collaboration as an alternative approach for documentation. We have learned about alternative methods, such as documentation as code, generating documentation, focusing on models, and the use of visual aids. Additionally, this chapter examined the adequacy of documentation and principles for good documentation, such as purpose-driven documentation, consumer-driven documentation, delivering just barely enough documentation, and the timely...