Teams build, test and deploy their code using consistent, automatic processes. Any required manual processes contribute significantly to technical debt. Manual build processes can be a major source of frustration and developer burnout, contributing significantly to turnover in teams. This is one of several critical habits that can eliminate that source of technical debt and the associated developer burnout.
✓ Critical ❑ Helpful ❑ Experimental
First steps to create this habit:
In addition to having tasks automated, it’s critical that the automation components are checked in to a source code management system and trigger builds as components are changed. This enables the team to have immediate feedback of all changes and alerts teams as early as possible should a problem arise.
Early detection leads to early, cheaper fixes
←Prev (Throw Out Before Add)(Tracer Bullet Development) Next→
Follow @growsmethod in the Fediverse, or subscribe to our mailing list:
Sign up for more information on how you can participate and use the GROWS Method®. We will not use your email for any other purpose.