More Ways to Reduce Cognitive Load
While the two organizational design patterns have a completely different impact on a software development team’s cognitive load, there are some guides that both could benefit from. Yet, it is our experience that these are easier to implement across the entire product group when there is fluid ownership across the entire tech stack of the product, versus when teams own technical pieces of the solution presented to customers. At the very least, there is no governing unit required to guide (or force) adoption and monitor compliance; it’s done by all for all. Even though some people might slack, others will pick up and educate the ones slacking.
- Standardization
- Architectural Guidelines
- Ubiquitous Language
- Dislocated Versus Co-Located Team Members
- Mob / Ensemble / Whole Team and Pair Programmnig
- Tidy Code and Architecture
- Small Changes by Means of Test Driven Development
- Continuous Integration
- Trunk Based Development
- Safety Nets by Means of Automated Testing
- Continuous Refactoring
- Focus on Learning, Learning Katas
- The Use of Generative AI