Team Structures and Infrastructure Pipelines

Infrastructure as Code: Delivering Dynamic Systems for the Cloud Age - Kief Morris

Topic 10 of 13

Published Aug 4, 2025 · Clip 37:20–41:57 (4:37)

Kief says team structure depends on organization size and maturity: small organizations should combine infrastructure with the development team, building only the minimum infrastructure needed, while larger organizations should split out infrastructure/platform teams with careful interaction models. He discusses pipelines: applications should be able to trigger the infrastructure provisioning they need, and a mature pattern treats infrastructure components like libraries—each component has its own pipeline that tests and stamps it into a repository that application teams can pull from. This enables self-service while satisfying governance concerns about teams building things like S3 buckets incorrectly.