Cultivating architecture with principles
Who is this presentation for?
- Architects and technical leads
Many organizations today strive to establish autonomous development teams who can move as independently of each other as possible. The goal is to achieve speed, scalability, and empowerment. The bigger you get, the less central decision making will work, because a central group just cannot know enough to make good decisions.
You have to decide what architecture governances look like in such a decentralized setup and how to avoid chaos. And you have to know how to walk the line between hard rules and helpful guidance. One way to create a shared understanding of what architecture means in your particular organization is to introduce architecture principles and use them to guide all the teams’ decision making toward common goals.
Birgitta Boeckeler explores different ways of creating and phrasing principles, outlines what you need in place around principles to make them practical and effective, and shares some lessons she’s learned from a few organizations where she’s seen principles in action.
- Experience delivering software on a team
What you'll learn
- Learn how to write architecture principles for your own organization's team
- Discover the importance of a guidance- and learning-based approach in architecture governance and the importance and different ways of communicating the “why” and “how come” of your architecture
Birgitta Boeckeler is a technical principal at ThoughtWorks, a global software consultancy, where she spends her time on software delivery teams with coding, architecting, coaching, and consulting. She’s been building software across all layers for more than 15 years, mainly in the space of large custom-developed websites.
Diversity & Inclusion Sponsor
For conference registration information and customer service
For more information on community discounts and trade opportunities with O’Reilly conferences
For information on exhibiting or sponsoring a conference
For media/analyst press inquires