> Markdown version of [/videos/1069-100-times-more-frequent-deployments-how-did-we-create-a-high-performance-team?t=912](https://www.wearedevelopers.com/videos/1069-100-times-more-frequent-deployments-how-did-we-create-a-high-performance-team?t=912). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# 100 times more frequent deployments: How did we create a high performance team?

Ditch asynchronous pull requests and embrace strict pair programming to unlock hyper-fast releases. See how high-trust engineering cultures deploy 100 times more frequently without breaking production.

- **Speakers:** [Mesut Ayata](https://www.wearedevelopers.com/@mesut-ayata)
- **Event:** World Congress 2024
- **Published:** August 20, 2024
- **Duration:** 27:31
- **URL:** https://www.wearedevelopers.com/videos/1069-100-times-more-frequent-deployments-how-did-we-create-a-high-performance-team

## Summary

Transitioning a large engineering team from sluggish bi-weekly release cycles with three-day code freezes to deploying over 100 times more frequently requires more than just modernizing a legacy tech stack. When faced with a highly coupled, monolithic application slowed down by manual quality checks and lengthy pull request approvals, engineering leadership must fundamentally rethink team dynamics. Measuring performance against core DORA metrics—deployment frequency, lead time, change failure rate, and time to restore—reveals that manual safety nets and waiting times often stifle developer productivity and actually increase the impact of systemic failures.

The pivotal shift involves abandoning traditional asynchronous pull requests in favor of trunk-based development to eliminate approval bottlenecks and integrate code continuously. Executing this safely demands migrating from after-the-fact code reviews to real-time collaboration through strict pair programming, effectively applying the four-eyes principle during active development. Coupled with automated Git commit hooks, default unit testing, and robust continuous integration, developers gain the confidence to merge directly into the main branch iteratively. Utilizing feature toggles allows incomplete code to bypass production exposure safely, empowering teams to deliver small, continuous updates without jeopardizing application stability.

Reaching a continuous delivery maturity level where a pipeline completes in just fifteen minutes hinges heavily on cultivating a high-trust, safe-to-fail culture based on the agile prime directive. Introducing these methods routinely triggers friction, as engineers accustomed to isolated coding must adapt to continuous collaboration and immediate feedback loops. Ultimately, successful modernization proves that standardizing ways of working, cross-skilling through daily tech huddles, and securing baseline team commitment matter far more than individual developer prowess. Connecting senior and junior engineers through pairing not only ensures immediate code quality but organically strips away bias, fostering an environment where rapid, reliable deployments become the daily standard.

**Keywords:** trunk-based development, continuous delivery maturity, pair programming practices, pull request bottlenecks, software deployment frequency, dora metrics optimization, high performance engineering teams, feature toggles implementation, automated git commit hooks, legacy application modernization, four eyes principle, agile prime directive, developer experience engineering, automated integration testing, continuous integration pipelines

## Chapters

1. **Identifying bottlenecks in monolithic application deployments** (00:02) — Legacy monolithic applications require manual checks and biweekly code freezes that slow down software delivery.
1. **Measuring software team performance using core DORA metrics** (05:03) — Crucial delivery indicators like deployment frequency help identify areas for reducing wait times.
1. **Establishing team alignment and foundational psychological safety** (07:36) — Fostering trust and shared working agreements prepares development teams for high-speed continuous delivery.
1. **Accelerating delivery workflows using trunk-based development** (11:24) — Replacing traditional pull requests with trunk-based development and test automation streamlines continuous integration workflows.
1. **Overcoming developer resistance to accelerate software deployments** (15:12) — Managing the inherent discomfort of process transitions helps teams successfully reach hundreds of monthly deployments.
1. **Addressing questions on development practices and testing strategies** (19:22) — Combining feature toggles, mutation testing, and pair programming mitigates the risks of accelerated deployment pipelines.

## Related Moments

- [Accelerating deployment cadences to improve software quality](https://www.wearedevelopers.com/videos/104-cloud-chaos-and-microservices-mayhem) (from "Cloud Chaos and Microservices Mayhem")
- [Overcoming cultural friction and scaling DevOps team practices](https://www.wearedevelopers.com/videos/855-fast-flow-not-fast-fluff-embracing-an-eclectic-devops-coaching-approach) (from "Fast Flow, Not Fast Fluff: Embracing an Eclectic DevOps Coaching Approach")
- [Evolving beyond DORA metrics for software delivery](https://www.wearedevelopers.com/videos/100026-building-10x-organizations-using-modern-productivity-metrics) (from "Building 10x Organizations Using Modern Productivity Metrics")
- [Analyzing how tech leaders deploy agile automation](https://www.wearedevelopers.com/videos/2081-ai-and-agility-the-dynamic-duo-for-disruption) (from "AI and Agility: The Dynamic Duo for Disruption")
- [Unifying core software principles for better team performance](https://www.wearedevelopers.com/videos/721-the-quest-for-better-software) (from "The QUEST for Better Software")
- [Integrating extreme programming with safe scaling frameworks](https://www.wearedevelopers.com/videos/200-agile-work-at-cariad-creating-a-customer-web-application-for-controlling-the-vehicle) (from "Agile work at CARIAD – Creating a customer web application for controlling the vehicle ")

## Related Articles

- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [Get Old, go Slow, Write Code!](https://www.wearedevelopers.com/magazine/81-get-old-go-slow-write-code)
- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub**
- [Principal Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1465908-principal-software-engineer-database-infrastructure) at **GitHub**
- [Staff Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1470125-staff-software-engineer-database-infrastructure) at **GitHub**
- [Senior Software Engineer](https://www.wearedevelopers.com/jobs/ext/159190-senior-software-engineer) at **GitHub**
- [Senior Software Engineer](https://www.wearedevelopers.com/jobs/ext/15942-senior-software-engineer) at **GitHub**