> Markdown version of [/videos/544-plan-ci-cd-on-the-enterprise-level](https://www.wearedevelopers.com/videos/544-plan-ci-cd-on-the-enterprise-level). 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).

---

# Plan CI/CD on the Enterprise level!

Stop debating pipeline syntax. Architect your enterprise CI/CD as an integrated engineering product to align stakeholders, optimize DORA metrics, and embed seamless security.

- **Speakers:** Pawel Piwosz
- **Event:** WeAreDevelopers LIVE
- **Published:** April 18, 2023
- **Duration:** 56:19
- **URL:** https://www.wearedevelopers.com/videos/544-plan-ci-cd-on-the-enterprise-level

## Summary

Designing enterprise CI/CD pipelines requires shifting focus from specific automation tools toward a holistic process architecture. Often, organizations simplify pipelines into linear steps—code, test, environments, and deployment—while neglecting the human and organizational behaviors that shape them. Recognizing Conway’s Law is essential to this approach; pipeline design inherently mirrors a company's internal communication structures, meaning isolated teams will almost inevitably build fractured or incompatible deployment workflows. Taking a helicopter view allows engineering leaders to architect CI/CD as an integrated value stream rather than a disjointed series of technical scripts.

Rather than debating pipeline syntax, engineering leaders must address foundational constraints like Team Topologies, automated quality gates, and branching strategies tailored to their specific system architectures. For instance, the difference between continuous delivery (which relies on manual approval gates) and continuous deployment (fully automated) dictates the entire testing and release rhythm of the organization. Furthermore, incident recovery methodologies require careful orchestration—such as managing a scenario where one team executes traditional rollbacks while a dependent service rolls forward. To manage this safely, organizations must synchronize Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO). By treating the CI/CD platform as an internal engineering product, teams can establish clear SLAs, SLOs, and SLIs to guarantee reliable operation for downstream engineering clients.

To optimize this deployment value stream, organizations must differentiate between operational monitoring (using open telemetry to spot transient errors) and process measurement. Utilizing DORA metrics—tracking deployment frequency, lead time, time to recover, and change failure rate—helps pinpoint exact systemic bottlenecks without acting on misleading symptoms. Furthermore, integrating security directly into this architectural framework ensures that modern compliance requirements are met seamlessly. This includes adopting secure identity providers over hardcoded credentials and generating Software Bill of Materials (SBOMs), which is shifting from a standard best practice to a strict federal and enterprise mandate. Ultimately, mapping these operational, technical, and human considerations creates a shared language—a translation layer aligning stakeholders, product architects, and security teams around a unified deployment strategy.

**Keywords:** ci/cd pipeline architecture, conway's law, team topologies, continuous delivery vs deployment, trunk-based development, value stream mapping, DORA metrics, SLA/SLO/SLI management, RTO and RPO strategies, rollback forward patterns, SBOM generation, automated quality gates, pipeline secret management, observability vs monitoring, internal platform engineering

## Chapters

1. **Shifting focus from tooling to pipeline delivery architecture** (00:03) — Designing deployment systems requires moving beyond specific platforms to optimize broader organizational efficiency.
1. **Influence of organizational structure on software systems** (03:10) — Conway's Law demonstrates how technical architectures mirror internal team communication and topology.
1. **Structuring environments and defining manual access limitations** (09:01) — Restricting engineering access to production forces tighter deployment automation and verifies reliable testing integrations.
1. **Aligning branching strategies with strict software architecture requirements** (10:48) — Determining if trunk-based or flow-based branching fits the technical constraints of monoliths versus serverless setups.
1. **Differentiating continuous delivery against continuous deployment models** (14:05) — Selecting deployment patterns like canary or blue-green requires balancing pipeline execution speed against comprehensive logic testing.
1. **Managing artifact storage policies under strict compliance regulations** (17:36) — Long-term object storage limits are shaped by stringent federal requirements and decoupled pipeline integrations.
1. **Defining automation limits through quality gates and escalation** (20:04) — Automating manual checks prevents execution delays while clarifying distinct ownership duties across complex lifecycles.
1. **Mapping operational capabilities against concrete business constraints** (22:25) — Internal networking boundaries and aggregate team experience metrics set immediate capability boundaries on integration tools.
1. **Managing operational responsibilities inside rigid manual release windows** (25:02) — Slow organizational approval committees and set maintenance schedules frequently throttle potential continuous deployment velocities.
1. **Executing granular deployment rollbacks and restoring stability objectives** (26:54) — Granular recovery strategies directly negotiate backward API compatibility parameters alongside required mean resolution timing.
1. **Establishing service level agreements directly for internal platforms** (28:58) — Treating engineering cohorts as direct software clients creates necessary service level reliability alongside dedicated monitoring nodes.
1. **Measuring systemic deployment success using standardized qualitative metrics** (32:05) — Tracking execution workflows and batch failure aggregates vividly exposes hidden process latency inside delivery methodologies.
1. **Selecting cohesive telemetry tooling for consistent pipeline visualization** (35:03) — Coupling separated continuous integration platforms necessitates deliberate execution logging to retain uniform monitoring insights.
1. **Securing functional pipelines across dependent package scans** (36:14) — Generating active software bills of material blocks embedded environment identity keys against critical node exploitation.
1. **Unifying engineering stakeholders around a shared deployment mindmap** (39:06) — Aligning disconnected architectural components mitigates cross-functional disputes by creating shared logic visibility for distinct domain experts.
1. **Exploring advanced observability stacks and distributed infrastructure challenges** (43:43) — Modern execution reliability requires flexible telemetry instrumenting, efficient automation parsing, and overcoming multi-cloud orchestration friction.

## Related Moments

- [Evaluating current trends in CI/CD pipelines](https://www.wearedevelopers.com/videos/333-cd2cf-continuous-deployment-to-cloud-foundry) (from "CD2CF - Continuous Deployment to Cloud Foundry")
- [Recapping vital capability shifts across security and enterprise infrastructure](https://www.wearedevelopers.com/videos/2097-ai-code-then-vs-now-from-complex-rubbish-to-co-piloting-in-12-months) (from "AI Code then vs now: From Complex rubbish to co-piloting in 12 months")
- [Building automated continuous deployment pipelines and final architectural insights](https://www.wearedevelopers.com/videos/100111-5-years-in-cloud-native-the-good-the-bad-and-the-bill) (from "5 Years in Cloud Native: The Good, the Bad, and the Bill")
- [Evolution of software delivery and the devops pipeline](https://www.wearedevelopers.com/videos/853-navigating-the-ai-wave-in-devops) (from "Navigating the AI Wave in DevOps")
- [Automating delivery pipelines and managing infrastructure via code](https://www.wearedevelopers.com/videos/545-my-journey-into-devops-world-how-it-all-started) (from "My journey into DevOps world - How it all started!")
- [Mapping the maturity roadmap for scaled devops adoption](https://www.wearedevelopers.com/videos/100018-from-devops-to-scaled-devops-how-we-re-rebuilding-continuous-delivery-as-a-platform) (from "From DevOps to Scaled DevOps: How We’re Rebuilding Continuous Delivery as a Platform")

## Related Articles

- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [Events like RSAC Get You CISOs. Developers Decide What Actually Gets Deployed.](https://www.wearedevelopers.com/magazine/693-events-like-rsac-get-you-cisos-developers-decide-what-actually-gets-deployed)
- [Walking Into The Era of Supply Chain Risks](https://www.wearedevelopers.com/magazine/106-walking-into-the-era-of-supply-chain-risks)
- [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production)

## Related Jobs

- [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub**
- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Lead Software Engineer - Data Engineering](https://www.wearedevelopers.com/jobs/ext/2000968-lead-software-engineer-data-engineering) at **Dynatrace**
- [Cloud Foundations Team](https://www.wearedevelopers.com/jobs/ext/1483289-cloud-foundations-team) at **GitHub**
- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**