Practice : Self-Service CI/CD Templates

Purpose and Strategic Importance

Self-Service CI/CD Templates enable faster, safer, and more consistent delivery by providing reusable, pre-approved pipelines and deployment workflows that engineering teams can adopt with minimal friction. By standardising CI/CD processes and embedding best practices into templates, teams reduce cognitive load, accelerate onboarding, and improve system reliability.

Without self-service templates, teams reinvent delivery pipelines, increasing inconsistencies, errors, and maintenance overhead, slowing down delivery and undermining confidence in release processes.

Description of the Practice

  • Central teams provide reusable, version-controlled CI/CD pipeline templates for common delivery scenarios (e.g. build, test, deploy, rollback).
  • Templates embed best practices such as automated testing, security scans, observability hooks, and rollback strategies.
  • Teams can adopt, customise, and deploy pipelines quickly without needing deep platform knowledge.
  • Updates to templates propagate improvements across teams consistently.

How to Practise It (Playbook)

1. Getting Started

  • Define common CI/CD requirements across teams and platforms.
  • Build initial templates using familiar tools (e.g. GitHub Actions, Azure DevOps, GitLab CI) with clear documentation.
  • Socialise templates with engineering teams and gather feedback.
  • Provide support channels for onboarding and troubleshooting.

2. Scaling and Maturing

  • Expand templates to cover a range of common patterns (e.g. microservices, data pipelines, infrastructure).
  • Integrate security, quality, and observability practices into templates by default.
  • Version control templates to manage improvements and deprecations.
  • Track adoption rates and feedback to guide continuous improvement.

3. Team Behaviours to Encourage

  • Treat pipeline templates as shared, evolving products.
  • Adopt templates to reduce duplication and inconsistency.
  • Provide feedback to improve templates rather than creating isolated solutions.
  • Share successes and learnings from using self-service pipelines.

4. Watch Out For…

  • Templates that are overly rigid or fail to meet diverse team needs.
  • Inconsistent adoption due to lack of support or communication.
  • Templates becoming outdated or misaligned with evolving best practices.
  • Poor documentation undermining the self-service experience.

5. Signals of Success

  • Teams onboard and deploy changes faster with minimal friction.
  • Delivery pipelines are consistent, reliable, and easy to maintain.
  • Quality, security, and observability practices are applied consistently across teams.
  • Platform teams receive fewer support requests due to streamlined, self-service delivery.