The document discusses building a quality system for software development. It begins by noting that while DevOps promises comprehensive testing throughout development and operations, in reality testing is often inconsistent due to a lack of focus and relentless pressure to deliver. It then outlines challenges in assigning responsibility for quality, having unfocused quality efforts, and dealing with increasing software complexity. The document proposes creating a quality system with three parts: specifying a quality strategy, defining a quality process, and automating testing. It provides examples of how to approach quality goals, roles, metrics, and investing in different phases. It emphasizes automating infrastructure, testing at all levels, and driving quality across the organization through communities of practice and continuous learning. Security quality is discussed as having its