GREEN BUILD POLICY EVERYTHING WHAT YOU MUST KNOW

I strongly believe that one of the reasons why people don’t give the importance they should to a “Green Build” is the fact that they don’t understand what is behind it; what does a “Green Build” bring to them and the organisation?
Having a “Green Build” means that a team has their basic needs fulfilled, which is to say that they don’t need to worry about basic problems like making sure that they have the right kits or the right packages in place.
Having a “Green Build” means that the team can concentrate on improving other parts of the software development, therefore focusing on something more important; to quote Deming, “Cease dependence on mass inspection to achieve quality. Improve the process and build quality into the product in the first place.”
A “Green Build” can serve as a safety net; if the code compiles, all the different tests pass, etc., it means that (most likely) nothing was broken, and this instils confidence in the team. The changes are not only visible to the other developers in the team, but they also feel as though they just “give birth” to a build that can potentially end up in acceptance testing or even in production.
If you want to continue you can see the rest of the article on my blog: https://luis-goncalves.com/green-build-policy/
My name is Luis Gonçalves and I am an Organisational Transformation Coachand I love to write about Agile Retrospectives, Agile Retrospectives Ideas, Scrum, the role Scrum Master, and Agile in general.
I have been creating Scrum Master Training for the agile community. If you are interested in knowing more or even working with me you can find me here: Agile Coach München.
