The description accompanying the video
During a previous coffee talk on Conway’s Law Nelis and Jurgen briefly touched upon the aspect of Architectures that could enable teams to truly collaborate in a shared code environment, avoiding Conway’s Law effects as much as possible.
This is an elaboration on the Architecture part, what are the key elements of an architecture that enables true collaboration? What other conditions does this depends on? Let’s share some real-life experience from a Mobile app development environment.
The video itself
- 00:00 Introduction to the subject
- 00:36 What topics are relevant in the context of Architectures that enable shared code ownership
- 02:16 The context that could make it work, team setup & work processes
- 05:18 The importance to share context in relation to architecture
- 05:57 The underlying architecture that enables multiple teams to work on the same mobile app
- 15:04 Enabling significant refactoring and continuously improve your code by isolating work environments
- 19:35 The guidelines for lower level architecture and evolutions within independent modules
- 27:58 Compliance versus evolution and socialising decisions or having architectural decision records
- 29:44 Supporting technical practices and processes to make it all work
- 43:50 Making the change towards this kind of architecture
The trigger for this conversion was a previous coffee talk on Conway’s Law.