Enabling constraints
An enabling constraint is a limitation or rule that, rather than hindering creativity or progress, actually promotes innovation and problem-solving. In software development, we've all experienced the positive effects of enabling constraints. Examples of enabling constraints in sw development are: trunk-based development continuous integration static code analysis/checks, i.e.: enforcing rules such as function or method length, number of parameters, naming conventions, etc Recently, I've been thinking about the use of enabling constraints at the organizational level. One example I think I heard here was about strengthening the cooperation between engineering and marketing. The solution can be remarkably simple: have marketing prepare the material for a feature before its implementation. What I was wondering is: how should we think about this change in terms of Team Topologies? Before diving into the topologies and interactions I would observe that this change adheres to som...