Site Antifragility Engineering

Site Antifragility Engineering

This is part 2 of a 3-part series on things I’ve learned working in an incubator together with a high-performing, truly agile software development team.

When I was working at an incubator a while ago, the distributed software teams released new features to production a few times a week. New functionality to the product was released continuously whenever the team assessed that it was ready for the public. It was the responsibility of the teams themselves to coordinate releases inbetween them, and also their collective responsibility to ensure the stability of the product. In other words and as explained in Part 1, the team was empowered by ownership of the release management pipeline.