Principles

Build Quality In

Quality software comes from quality people. Therefore, Poor quality software must come from poor quality people. To build quality in, we remove the things that reduce quality.

Work in Small Batches

Too many releases are hard to report and manage. To reduce the number of updates to the Release Tracking spreadsheet, we should focus on a small number of releases each quarter. This provides us with more time to Amplify Feedback.

Limit WIP

Workers Idle Problem is when workers are idle, that’s a problem. We should ensure everyone is planned at 120% capacity. Having these stretch goals ensures everyone exerts maximum effort. This ensures no idle downtime, which intuitively, is waste. Limiting WIP is a key foundation to how we ensure you are maximizing capacity utilization in our organization. This also helps to ensure that time in the Coding Pool remains as short as possible.

Amplify Feedback

Coaching employees is an important daily practice to ensure they know we are tracking their work and care about their output.

Everyone is Responsible

Each Code Engineer is responsible for their own work and should be rewarded for the work they do. If a feature is successfully delivered, we should identify the Code Engineer who made the most changes and give them a bonus. It would be unfair to reward the whole team based on the excellence of an individual.

Psychological Safety

When we need to help resources with the opportunity to find positions with other organizations, we use the PeopleWare HRaaS system. This uses individual performance data and machine learning models to automate the process of giving them that opportunity. This allows us to avoid the stress of challenging conversations.

Systems Thinking

The Scaled Agile DevOps Maturity Framework is built upon systems thinking. There are two systems that operate within the SADMF System. The System of Authority (SOA)* (SOA) and the System of Service (SOS)* (SOS). Both Systems are accountable to the Admiral’s Transformation Office (ATO)*.