Scaling Software Integrity with Automated Code Verification | Sonar Summit 2026

The Challenge of Maintaining Quality at Scale

As software development accelerates, organizations face a critical challenge: how to maintain code quality without sacrificing development velocity. John Clifton, Product Manager at Sonar, explored this dilemma with Paul Edwards, DevSecOps Architect at Wolters Kluwer, during the Sonar Summit 2026. Their conversation revealed how Wolters Kluwer's tax and accounting business successfully transformed its approach to software quality across a large European portfolio spanning multiple countries and teams.

Identifying the Problem: Fragmented Quality Standards

Before implementing comprehensive changes, Wolters Kluwer operated with fragmented quality standards across its organization. Technical debt was managed at the local team level, resulting in inconsistent visibility and varying levels of accountability. Different teams had different levels of technical debt and different approaches to managing it, making it impossible to assess the organization's overall quality posture at the portfolio level. Leadership lacked the visibility needed to understand where the organization stood and where teams should focus their efforts. This fragmentation created what Edwards described as a situation where "we didn't know what we didn't know" from an executive perspective.

The Transformation: Shifting Quality Left

Wolters Kluwer's solution involved implementing non-negotiable security and quality standards uniformly across all European products and teams. The cornerstone of this transformation was adopting SonarQube to enforce quality gates at the pull request stage, preventing technical debt from accumulating in master branches. Rather than identifying issues after code was merged and accumulated in remediation backlogs, the organization shifted to a "quality left" approach where standards were applied to every change before it entered the codebase. This meant developers had to meet consistent, baseline quality standards before code could be merged—a significant cultural shift from the previous model where teams managed technical debt after the fact.

Building Developer Adoption and Organizational Benefits

Surprisingly, developer adoption came more easily than expected. Teams recognized the benefits of immediate feedback during their development workflow rather than context switching later to fix accumulated issues. By integrating quality checks directly into existing tools like GitHub and Azure DevOps—rather than requiring developers to navigate to separate platforms—the organization made quality gates frictionless. Additionally, the standardized approach created unexpected organizational benefits: developers could now move seamlessly between teams and products because they encountered consistent processes and standards everywhere. This eliminated resource silos and improved flexibility in resource allocation across the organization.

Tangible Results and Stakeholder Buy-In

The implementation eliminated awkward conversations between technology and product teams about technical debt management interrupting feature delivery. Since quality checks were now embedded in the development process itself, technical debt prevention became part of the normal workflow rather than a competing priority. Both leadership and engineering teams saw measurable benefits: executives gained visibility into portfolio-wide quality metrics, while developers appreciated the instant feedback within their IDE extensions and the collaborative review process. The organization achieved significant reductions in scan times while maintaining—and improving—overall code quality standards.

Key Takeaways

• Shift left prevents accumulation: Enforcing quality gates at the pull request stage stops technical debt from entering the codebase, eliminating costly downstream remediation cycles
• Developer experience drives adoption: Integrating quality feedback directly into existing development tools and IDEs increases compliance and reduces friction in the development workflow
• Standardization enables flexibility: Consistent quality standards and toolchains across the organization allow developers to move between teams and products without relearning processes
• Visibility supports governance: Portfolio-level metrics and centralized quality standards provide leadership with the visibility needed to make informed decisions about resource allocation
• Prevention beats remediation: Implementing automated code verification prevents technical debt accumulation more effectively than addressing accumulated debt after the fact