As a Team Lead in a fairly talkative organisation, I attend a lot of meetings. However valuable these discussions may be, this presents a couple of challenges for the team.
In software development, quick feedback is fundamental, and continuously building, testing and deploying is part of our standard toolkit.
But it isn’t enough to set up and run these processes; we need to pay attention to the results. If we can’t successfully build, test and deploy our software, then we have no idea whether we’re building it right, and we risk releasing broken components. It saddens me how often I see teams that have become completely inured to failures, and the result is a predictable decline in quality and drop in team effectiveness.
Here then are a few quick and easy techniques to start paying attention to these failures.