-
Notifications
You must be signed in to change notification settings - Fork 0
Product Governance
This article focuses on
- Product Mindset
- Team maturity
- DevSecOps
- Decentralization
Its an idea of brining Development + Security + Operations together.
The following are key factors from the twelve-factor app pattern methodology that play a role in adopting a product mindset for delivering software:
- Build, release, run – Engineers adopt a devops culture that allows them to optimize all three stages.
- Config – Engineers build better configuration management for software due to their involvement with how that software is used by the customer.
- Dev/prod parity – Software treated as a product can be iteratively developed in smaller pieces that take less time to complete and deploy than long-running projects, which enables development and production to be closer in parity
Adopting a product mindset is driven by culture and process—two factors that drive change. The goal of your organization’s engineering team should be to break down any walls between the engineers who build the code and the engineers who run the code in production. The following concepts are crucial:
- Automated provisioning – Operations should be automated rather than manual. This increases velocity as well as integrates engineering and operations.
- Self-service – Engineers should be able to configure and provision their own dependencies. This is enabled by containerized environments that allow engineers to build their own container that has anything they require.
- Continuous Integration – Engineers should check in code frequently so that incremental improvements are available for review and testing as quickly as possible.
- Continuous Build and Delivery – The process of building code that’s been checked in and delivering it to production should be automated so that engineers can release code without manual intervention.
Containerized microservices help engineering organizations implement these best practice patterns by creating a standardized format for software delivery that allows automation to be built easily and used across a variety of different environments, including local, quality assurance, and production.