Setting hard boundaries is completely absent from software management and so essential to productivity and job satisfaction. In the military we call this staying in your lane or knowing your left and right limits.
This concept is often easily achievable through automation by removing the flexibility to allow knowingly bad practices. Such techniques are code validation rules, interfaces, method removal/redefinition and so forth. It provides a clear sense of direction by removing distractions and bad conveniences as passable options.
The concept also sets hard business limits on what work a team performs without intermingling in the responsibilities of other teams.
I am amazed at how absent this concept is to software given that it is so foundational to project management.
This concept is often easily achievable through automation by removing the flexibility to allow knowingly bad practices. Such techniques are code validation rules, interfaces, method removal/redefinition and so forth. It provides a clear sense of direction by removing distractions and bad conveniences as passable options.
The concept also sets hard business limits on what work a team performs without intermingling in the responsibilities of other teams.
I am amazed at how absent this concept is to software given that it is so foundational to project management.