Software Architecture Metrics

Chapter 6. Scaling an Organization: The Central Role of Software Architecture

João Rosa

I’m a student of sociotechnical systems and complexity theory. Although I’m a software engineer at heart, I love the challenges that arise from the intersection of people, technology, and underlying processes: sociotechnical systems. Being able to contribute and have a positive impact on the systems of which I’m a part is what makes me get out of bed every day. I believe that chief technology officers (CTOs) and chief product and technology officers (CPTOs) should understand and contribute to their sociotechnical systems, enabling the people and teams around them to excel in their areas of expertise.

I’ve distilled my software architecture practices by serving in different roles, including software engineer, manager, software architect, consultant, and CTO. I specialize in digital companies that make a difference in people’s lives. More specifically, I mainly work with scale-ups, organizations that have proven their products are accepted in a market and are looking to scale to multiple markets or start new products. I’m writing this chapter with my “CTO goggles” on, speaking from a strategy implementation viewpoint so that I can connect the concepts of software architecture and metrics—that is, how to measure your progress toward your goals—to the rest of the organizations they affect. This holistic approach is intended to offer a coherent experience across the organization, where employees ...