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

Chapter 9: Architecting for Quality with Quality Attributes

"Architecture should speak of its time and place, but yearn for timelessness."

– Frank Gehry, architected the iconic Dancing House in Prague

The previous chapter explained the DevOps and automation segment of technical agility by examining the importance of fostering DevOps culture and architecting for continuous delivery. This chapter will focus on the third segment of technical agility – built-in quality.

Mission-critical applications must be anti-fragile and consistently deliver services without degradation of quality. Failures can have severe consequences for the business, such as revenue loss, customer dissatisfaction, and even, in some cases, health and safety issues. Therefore, a methodological approach for building quality into the software development process is crucial. To achieve this, we need to learn a mechanism of connecting measurable business outcomes such as revenue loss to...