PART III CONCLUSION

Within the previous chapters of Part III, we have implemented the architecture and technical practices that enable the fast flow of work from Dev to Ops, so that value can be quickly and safely delivered to customers.

In Part IV: The Second Way: The Technical Practices of Feedback, we will create the architecture and mechanisms to enable the reciprocal fast flow of feedback from right to left, to find and fix problems faster, radiate feedback, and ensure better outcomes from our work. This enables our organization to further increase the rate at which it can adapt.

Additional Resources

The Unicorn Project, the companion novel to The Phoenix Project, illustrates first hand the experiences of a developer looking to improve, among other things, the flow of work (itrevolution.com/the-unicorn-project/).

Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations succinctly brings all the research from four years of State of DevOps Reports together and effectively shows what metrics lead to better quality software (itrevolution.com/accelerate-book)

Jez Humble and David Farley’s Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation remains a must read for anyone in Development or Operations.

Elisabeth Hendrickson’s Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing is an excellent source to help you figure out how to build effective tests.

And Martin Fowler’s blog explaining his Strangler Fig Application Pattern is still an essential read. (martinfowler.com/bliki/StranglerFigApplication.html).