Enable javascript in your browser for better experience. Need to know to enable it? Go here.

Facilitating Software Architecture

Empowering teams to make architectural decisions
Facilitating Software Architecture book cover

Bridge the gap between architects and software developers

 

As software architecture has become more and more complex, ever closer collaboration between architects and software developers has become critical. 

 

However, this isn't easy to do — developers need to learn new skills and concepts and architects need to think differently about their role in designing and evolving these systems.

 

This book from Thoughtworker Andrew Harmel-Law demonstrates that bridging the gap between architect and developer is possible. Laying down the conceptual underpinnings for a better approach and outlining practical steps that teams can take today, it opens up a new route to overcoming a key problem facing technology teams in every industry: architecture is just too demanding to be practiced by a single job role.

Decentralize trust
Support developers to take informed architectural decisions with confidence.
Establish architectural principles together
Build alignment and collaboration by exploring and evolving your key principles.
Leverage your own technology radar
Build a collective picture of the technologies you use and ones you want to use.
Manage architectural variability
Discover strategies to enable consistency and increase predictability across a complex system.
Share power and promote accountability
Manage the cultural change needed to make all technologists part of architectural decisions.
Make decisions clear and transparent
Learn how to leverage architecture decision records for clarity and transparency.
Decentralize trust

Support developers to take informed architectural decisions with confidence.

Establish architectural principles together

Build alignment and collaboration by exploring and evolving your key principles.

Leverage your own technology radar

Build a collective picture of the technologies you use and ones you want to use.

Manage architectural variability

Discover strategies to enable consistency and increase predictability across a complex system.

Share power and promote accountability

Manage the cultural change needed to make all technologists part of architectural decisions.

Make decisions clear and transparent

Learn how to leverage architecture decision records for clarity and transparency.

Read a free chapter

Take a look inside Facilitating Software Architecture with this free chapter.

 

Learn how a technology radar — like the Thoughtworks Technology Radar — can help you make better architectural decisions collectively.

 

Read using the PDF viewer or click the button below to download the PDF to your machine.

Andrew Harmel-Law, Thoughtworks

About the author

 

Andrew Harmel-Law is a Principal at Thoughtworks. He specializes in agile delivery, domain-driven design, build tools and automation. His experience spans many sectors including government, legal, finance and retail.

 

He's an active member of the wider software community and seeks out opportunities to share his experiences and perspectives. 

 

Andrew also contributed to Software Architecture Metrics, published in 2022 by O'Reilly.

Explore a snapshot of today's technology landscape