Develop the right combination of processes and technical excellence to address architectural challenges
Explore a range of architectural techniques to modernize legacy systems
Discover how to design and continuously improve well-architected sustainable software

Description

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.

Who is this book for?

This agile study guide is for architects currently working on agile development projects or aspiring to work on agile software delivery, irrespective of the methodology they are using. You will also find this book useful if you're a senior developer or a budding architect looking to understand an agile architect's role by embracing agile architecture strategies and a lean-agile mindset. To understand the concepts covered in this book easily, you need to have prior knowledge of basic agile development practices.

What you will learn

Acquire clarity on the duties of architects in Agile development
Understand architectural styles such as domain-driven design and microservices
Identify the pitfalls of traditional architecture and learn how to develop solutions
Understand the principles of value and data-driven architecture
Discover DevOps and continuous delivery from an architect s perspective
Adopt Lean-Agile documentation and governance
Develop a set of personal and interpersonal qualities
Find out how to lead the transformation to achieve organization-wide agility

What do you get with eBook?

Instant access to your Digital eBook purchase

Download this book in EPUB and PDF formats

Access this title in our online reader with advanced features

DRM FREE - Read whenever, wherever and however you want

AI Assistant (beta) to help accelerate your learning

Frequently bought together

$54.99

Software Architecture for Busy Developers

$38.99

$54.99

Total $ 148.97

Filter reviews by

All

Amazon verified reviews

Carlos Gamboa Nov 01, 2024

Too verbose

Amazon Verified review

Muhad Aug 14, 2021

Good read for enterprise and solution architects as the book touches upon many practical scenarios faced by architects in the current lean and agile ways of working.Well organized content with real world examples and lots of excellent references throughout the book on different subjects.

AMol SOlanki Jul 09, 2021

A must read for all new/aspiring software architects. Good thing about the book is that, the author includes many references which support his writing. Evidence backs every point.This book has four sections: introduction, how the architect fits into the organization, the role in details, and the architect as a person. At the very start of the book, Author introduces his Agile Architect's Lens with twelve focal points representing the knowledge of key segments and leading practices for Agile architects to successfully operate in an Agile organization. The book also covers key architect roles and explains their duties in Agile software development projects.As someone dealing with enterprise level software architecture, you can ask yourself a lot of things. The questions just comes up. It doesn't always look so good with answers. This book answers those questions you don't normally ask yourself. This book provides a highly readable and comprehensive overview of agile architecture suitable for aspiring and practicing software architects, as well as software developers eager to learn about agile principles.

C. Gary Rupp Jul 01, 2021

Expanding on the concepts behind Evolutionary Architectures, Rajesh R V has written a book That goes into much more detail on why fully architected solutions and 'Big Upfront Designs' (BUFD) are doomed to failure. The iterative and incremental development models of agile are here to stay. Unfortunately, many Agile practices seemingly discount the importance of architecture and design, and that too is a mistake.The better approach is to build architectures and designs iteratively and incrementally, just in time to support product development. Rajesh makes the point that Agile architecture is a combination of doing architecture using Agile methodologies, as well as building resilient architecture to meet evolving customer needs. We need to build software faster while balancing sustainability and not create more tech debts in the process.Rajesh promotes the use of intentional architecture and emergent design as the way forward to build sustainable products in an Agile World. Intentional architectures create purposeful and planned build strategies to enhance solution design, performance, and usability and enable multiple team designs to synchronize and integrate their development efforts. Emergent design allows the development organization to start delivering functionality immediately, and lets the design emerge as needs are exposed.At the very start of the book, Rajesh introduces his Agile Architect's Lens with twelve focal points representing the knowledge of key segments and leading practices for Agile architects to successfully operate in a Lean-Agile organization to design continually evolving solutions. The book then dives into each focal point in sufficient detail through the remaining chapters. The book also covers two key architect roles – enterprise architect and solution architect, explaining their duties in Agile software development projects.There are not many practical books on the application of architecture values, principles, and strategies in support of Lean-Agile and DevOps-based software delivery organizations. And though several of the Lean-Agile frameworks (SAFe, LeSS, and DA) discuss the importance of architecture, they do not provide the practical implementation details found in this book. If you are an aspiring Agile architect, this book should be in your library.Cecil Gary Rupp

Binildas Jun 24, 2021

I would like to thank Packt for sharing me a copy of this book by Rajesh for review.I have covered more than 75% of the book in the first few days itself, yet to finish it. The best part of the book is that there are not much literature in the book format which talks about Architecture recipes with an agile perspective. The book sets a broad platform covering the length and breadth of different aspects of Architecture.The reader after covering the topics however has to read further to understand the details to implement, however that's not the intend of this book to cover. To quote an example, when the author says that "Let's say the initial plan for the first year is to only handle Cessna-type aircraft, which only need a runway length of 2,000 feet. There is no point in building an 8,000-foot runway upfront as it is not going to add any business value.", the author also makes it a point to mention that "we need to have an architecture intent to build an 8,000-foot runway" - I would say, adding the "intend" to the checklist is the first and important part for an Architect - if that's done at the "right time", details or intricacies on how to action on that intend can take its natural time and effort.There are few other areas where as a reader I have slightly different point of view to mention. To quote another example, when the author says "In the early 2000s, the abstract database factory was a common pattern, as many architects believed that they needed to cater to multiple databases such as MySQL, Oracle, and so on, but in reality, the need does not" - I do agree that Over engineering is a symptom which we need to avoid, but the boundary of enough vs. over is sometimes blurred, depends on context. I have experience in working on reengineering exercises on 20 year old systems getting migrated from Vendor's stack DB to Open Source DB - we were not compelled to throw away the system, since "just enough" abstractions paid off. However, my understanding after reading is that the author is not against enough engineering, author is trying to make a point on over engineering.Overall, the book provides a nice coverage on many aspects for an agile Architecture process. It will help a grooming Architect to decide and design for priorities. It will also help experienced Architects to reform his existing blanks (Architecture templates) using new approach of processes.

Becoming an Agile Software Architect: Strategies, practices, and patterns to help architects design continually evolving solutions

What do you get with eBook?