Scaling Teams Mobile Development — The Mental Model
<p>In the article <a href="https://medium.com/microsoft-mobile-engineering/scaling-teams-mobile-development-evolving-the-design-pattern-c3c8ff53facb" rel="noopener">Scaling Teams Mobile Development — Evolving the design pattern</a> we explored how multiple partner teams working on a large code base can be streamlined by employing the contributor design pattern. I decided to write this article as a prequel. In this article we will discuss the problem statement in a more generic way and draw some parallels with popular design patterns.</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:700/1*U1-R54TrsO7jiBTWOieDSw.jpeg" style="height:467px; width:700px" /></p>
<p>Photo by <a href="https://unsplash.com/@xavi_cabrera?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText" rel="noopener ugc nofollow" target="_blank">Xavi Cabrera</a> on <a href="https://unsplash.com/photos/kn-UmDZQDjM?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText" rel="noopener ugc nofollow" target="_blank">Unsplash</a></p>
<p>We started with the following mission statement in mind:</p>
<p><a href="https://medium.com/microsoft-mobile-engineering/scaling-teams-mobile-development-the-mental-model-8224afb1e4ba"><strong>Read More</strong></a></p>