| Area |
Goal |
Principle(s) |
| Alignment |
We prioritize according to business objectives. |
Culture |
| Alignment |
We volunteer for tasks rather than having them assigned. |
Culture |
| Alignment |
Our team has clear objectives that correspond with our company vision. |
Culture Measurement |
| Alignment |
Our product team is focused on sustainable velocity rather than current speed. |
Culture Automation Measurement |
| Alignment |
We focus on time to repair rather than time between issues. |
Culture Measurement |
| Alignment |
DevOps is not isolated to a specific role in our organization. |
Culture |
| Alignment |
DevOps is not isolated to a specific team in our organization. |
Culture |
| Alignment |
Our operational functions are seen as a source of competitive advantage. |
Culture |
| Context |
Representation from our operations team is involved in development sprint planning. |
Culture Sharing |
| Context |
We make potential changes visible to all members of our product team. |
Culture Sharing |
| Context |
We have an automated system for running tasks and receiving notifications with our team chat. |
Culture Sharing |
| Context |
We consult with auditors and regulators regularly and seek guidance when designing systems. |
Culture Sharing |
| Context |
Our team is encouraged to question tasks and priorities. |
Culture Sharing |
| Context |
We have a centralized instant message system including all members of our product team. |
Sharing |
| Context |
All members of our product team have access to environment status, metrics and history. |
Sharing Measurement |
| Context |
All members of our product team have access to code status, metrics and history. |
Sharing Measurement |
| Learning |
We cultivate an environment of continuous learning. |
Culture |
| Learning |
We regularly celebrate our product team’s learnings and success internally. |
Culture |
| Learning |
We regularly share our product team’s learnings and success with the rest of our organization. |
Culture Sharing |
| Learning |
We openly discuss failures in order to share learning. |
Culture Sharing Measurement |
| Learning |
We identify skills needed to improve or address future objectives. |
Culture Measurement |
| Learning |
We strive to examine how we complete our work, and how effectively we complete it. |
Culture Measurement |
| Learning |
We estimate based on measurement and past experience. |
Measurement |
| Lifecycle |
Our software development cycle is 2 weeks or less. |
Culture |
| Lifecycle |
Our software development cycle is defined by releasing a working change into production. |
Culture Measurement |
| Lifecycle |
We stop development upon discovering a defect and prioritize its repair. |
Culture |
| Lifecycle |
Developers or product owners are able to deploy our product to production. |
Culture Automation |
| Lifecycle |
We have automated testing prior to automated production deployment. |
Automation Testing |
| Lifecycle |
Our configuration of systems is automated. |
Automation |
| Lifecycle |
Our deployed system configuration is immutable. |
Automation |
| Lifecycle |
Our release and deployment automation is environment agnostic. |
Automation Testing |
| Organization |
Our subject matter expertise is not isolated to individuals. |
Culture Sharing |
| Organization |
We enable peer and cross-functional review for changes. |
Culture Sharing Testing |
| Organization |
Our organization is configured around cross-functional teams. |
Culture |
| Organization |
Our teams are customer and product oriented. |
Culture |
| Organization |
We review priorities on a regular basis. |
Culture Sharing |
| Organization |
Our developers have access to production-like systems to work and test on. |
Automation Testing |
| Organization |
Our developers have access to production-like data to work and test against. |
Automation Testing |
| Organization |
Our developers have access to dependencies required to build and test software. |
Automation Testing |
| Process |
Our organization follows agile development practices. |
Culture |
| Process |
We practice blameless postmortems. |
Culture Sharing |
| Process |
We regularly examine constraints in our delivery process. |
Culture |
| Process |
Our system configuration is committed into version control. |
Automation Testing |
| Process |
Our documentation is version controlled and shared. |
Sharing |
| Process |
We maintain a backlog of tasks, visible to all team members and available for comment. |
Culture Sharing Measurement |
| Process |
We practice test or behaviour driven development. |
Testing |
| Process |
We test our changes against a merge with our mainline code. |
Testing |
| Process |
We test our changes against production-equivalent load and use patterns. |
Testing |