You're reading from Becoming an Agile Software Architect Strategies, practices, and patterns to help architects design continually evolving solutions

Product type Paperback

Published in Mar 2021

Publisher Packt

ISBN-13 9781800563841

Length 372 pages

Edition 1st Edition

Tools

JIRA

Concepts

Agile

Author (1):

Rajesh R V

View More author details

Table of Contents (19) Chapters

Preface

1. Section 1: Understanding Architecture in the Agile World

2. Chapter 1: Looking through the Agile Architect's Lens FREE CHAPTER

3. Chapter 2: Agile Architecture – The Foundation of Agile Delivery

4. Section 2: Transformation of Architect Roles in Agile

5. Chapter 3: Agile Architect – The Linchpin of Success

6. Chapter 4: Agile Enterprise Architect – Connecting Strategy to Code

7. Chapter 5: Agile Solution Architect – Designing Continuously Evolving Systems

8. Section 3: Essential Knowledge to Become a Successful Agile Architect

9. Chapter 6: Delivering Value with New Ways of Working

10. Chapter 7: Technical Agility with Patterns and Techniques

11. Chapter 8: DevOps and Continuous Delivery to Accelerate Flow

12. Chapter 9: Architecting for Quality with Quality Attributes

13. Chapter 10: Lean Documentation through Collaboration

14. Chapter 11: Architect as an Enabler in Lean-Agile Governance

15. Section 4: Personality Traits and Organizational Influence

16. Chapter 12: Architecting Organizational Agility

17. Chapter 13: Culture and Leadership Traits

18. Other Books You May Enjoy

Keeping options open

Architecture work starts far ahead of the LRM, as shown in Figure 6.8. During this period, architects can use multiple approaches to explore solutions for decision making.

This section will examine a few techniques to refine the decision backlog to arrive at a final solution by analyzing options. In some cases, we have to eliminate options early, but in other instances, techniques that keep as many options open as possible are more appropriate.

Using a hypothesis-based solution

A Hypothesis-Based Solution (HBS) is a structured mechanism for exploring, analyzing, and finalizing solutions based on point-based design. The HBS approach is particularly useful in cases where the architect is confident about a particular solution, based on experience and expertise, even before all the requirements are known.

In such cases, architects start with one potential solution and keep exploring that solution further with an open mind until they discover negative cases...