

# [OA.STD.6] Provide teams ownership of the entire value stream for their product
<a name="oa.std.6-provide-teams-ownership-of-the-entire-value-stream-for-their-product"></a>

 **Category:** FOUNDATIONAL 

 Establish teams that are able to own their respective value streams and products. These teams follow a *you build it, you run it* approach, as coined by Werner Vogels in 2006. The team responsible for building a system should also be responsible for running, maintaining, and overall owning it. At Amazon, we call these small, autonomous teams with a single-threaded focus [two-pizza teams](https://docs.aws.amazon.com/whitepapers/latest/introduction-devops-aws/two-pizza-teams.html). This approach minimizes handoffs and makes teams both the creators and custodians of their products. 

 Value stream ownership does not mean preventing teams from working together. These teams not only own the development of their product, but also take responsibility of aspects like security and quality assurance. To be successful in this model at scale, centralized functions, such as centralized security teams, must also evolve: instead of direct oversight, they should act as enablers, providing resources and expertise to these distributed teams. 

 The enabling functions should provide the necessary knowledge, resources, and attention required for teams to be successful. Individual teams build relationships with the centralized functions, share knowledge, and enhance processes consistently over time. This ultimately leads to improved outcomes for their products, customers, and the organization. Invest in ongoing cross-functional training to help individual team members acquire skills that will make them successful within their value streams. This training could include teaching developers to be security-minded, or teaching security resources to develop. Over time the teams should gradually become more self-reliant, collaboration between teams should improve, and deployment frequency should increase. 

**Related information:**
+  [AWS Well-Architected Security Pillar: SEC11-BP01 Train for application security](https://docs.aws.amazon.com/wellarchitected/latest/framework/sec_appsec_train_for_application_security.html) 
+  [AWS Well-Architected Security Pillar: SEC11-BP08 Build a program that embeds security ownership in workload teams](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/sec_appsec_build_program_that_embeds_security_ownership_in_teams.html) 
+  [Enterprise DevOps: Why You Should Run What You Build](https://aws.amazon.com/blogs/enterprise-strategy/enterprise-devops-why-you-should-run-what-you-build/) 
+  [Amazon's approach to security during development: Ownership](https://youtu.be/NeR7FhHqDGQ?t=632) 
+  [Amazon's approach to security during development: Security Review Process](https://youtu.be/NeR7FhHqDGQ?t=1285) 
+  [Powering Innovation and Speed with Amazon's Two-Pizza Teams](https://aws.amazon.com/executive-insights/content/amazon-two-pizza-team/) 
+  [The Amazon Software Development Process: DevOps Teams](https://youtu.be/52SC80SFPOw?t=387) 