Developer guidelines that cut defects

Post-deployment defects down 20% year on year, for three years running.

Role: Governance lead · Platform: ServiceNow

Developer guidelines: before and after Before: a new team of developers with no development standards, each developer using their own conventions, which led to unreadable code, unclear change ownership, longer development cycles, disputes in code review and growing technical debt. Better tools and more developers were considered, but the fix chosen was rules and conventions: fix the leaking bucket, do not add water. After: one shared framework of coding standards, naming conventions, update set rules, processes, code review standards and checklists. Post-deployment defects fell 20 percent year on year for three years, and reviews and finding custom scripts got faster. BEFORE A new team, and everyone coding their own way Dev 1 Dev 2 Dev 3 Dev 4 Dev 5 • Unreadable code, unclear change ownership • Longer development cycles • Disputes in code review • Growing technical debt HOW Fix the leaking bucket, don’t add water Better tools More developers Rules and conventions Considered, then set aside Chosen AFTER One shared framework Coding standards Naming conventions Update set rules Processes Code review standards Checklists Post-deployment defects Start Year 1 −20% Year 2 −20% Year 3 −20% Down 20% year on year, three years running. Faster reviews, and custom scripts easier to find.

Context

The team was new, and there were no development standards. Each developer used their own conventions, so every script read differently and things were hard to find.

Problem

Code became hard to read, and it was difficult to tell who had changed what. Development cycles ran longer, code reviews sometimes turned into disputes, and technical debt kept building.

Decision

We looked at better tools and more developers. But the real problem was rules and conventions, not capacity. If a bucket is leaking, pouring in more water won't help; it drains anyway. We needed to fix the bucket.

What we built

  • Coding standards and naming conventions.
  • Update set rules.
  • Code review standards, including how often reviews happen.
  • Development processes and checklists.

Result

  • Post-deployment defects, as logged in Jira, down 20% year on year for three years.
  • Less time spent in code reviews.
  • Faster to find custom scripts and work through update sets.

What I'd do differently

There is no one-size-fits-all framework. Next time I'd shape the guidelines around the organisation's own culture and practices from the start, and keep updating them as ServiceNow evolves.