Software architecture requires balance. During the 20 years I’ve been leading technology organizations to build products, mostly via Agile, I’ve learned some rules that have helped me — and my teams — successfully strike the right balance. These aren’t technically focused rules; they’re more generic, so they apply to monolithic, layered, service-oriented, and microservice architectures equally well. One of these rules is the subject of this Advisor.
Advisor
About The Author
Bob Galen is an Agile methodologist, practitioner, and coach. In this role, he helps guide companies and teams in their pragmatic adoption and organizational shift toward Scrum and other Agile methods. Mr. Galen is currently a Principal Agile Coach at Agile Moose. He regularly speaks at international conferences and for professional groups on a broad range of topics related to Agile software development. Mr. Galen is the author of Agile… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.