Admirals Transformation Office (ATO) #

This is the heartbeat of the transformation, it is the command-and-control center to ensure everyone is achieving the goals of SADMF. It is accountable for the 5-8 transformation roadmap, assessments, metrics, certification renewals, and general project management of the transformation. The ATO is led by the Admiral, who commands all direction, innovation, and methodology implemented at scale.

Build Engineers (BE) #

These YAML experts are responsible for dictating to the Code Engineers how the build should work and writing the YAML to make that happen. Updating commands in YAML takes away from feature delivery and Code Engineers should focus on features.

Change Rejection or Acceptance Party (CRAP) #

The CRAP is responsible for reviewing all changes and rejecting any changes that do not meet the iteration standards set by the Admirals Transformation Office or that does not have the change checklist filled in correctly. The CRAP will also be responsible for accepting changes that meet the standards and are ready to be included in the next Convoy. The meeting dias should contain seven people from areas without knowledge of the systems being changed to ensure that the proper levels of detachment and objectivity can be maintained. They will meet twice per week and all approval decisions must be by unanimous secret vote. Meeting supplicants will take an oath that they have applied all of the controls on the checklist.

Chief Signals Officer (CSO) #

This senior executive is responsible for tracking and reporting our adherence to the plan by publishing the Feature Completion Ratio daily.

Code Standards Enforcement Team (CSET) #

Code Engineers are too close to the problem to effectively review the code they write. Additionally, reviewing code takes time away from coding. To resolve this, the CSET will perform all code reviews. The CSET is also responsible for defining and enforcing all coding standards for the enterprise. This includes, but is not limited to:

• Indentation depth
• Using tabs vs. spaces
• Use of approved EARB variable and method names
• Comment format

Code Engineer (CE) #

This role is the backbone of a SAD implementation. The job of the Code Engineer is to transform requirements into machine-readable instructions quickly and quietly. Code Engineer expertise can be judged by the number of questions. Since a Code Engineer is expected to be an expert at data structures and algorithms, fewer questions indicate more expertise.

Commodore (C) #

The Commodore is responsible for collecting status reports for the Convoy and ensuring all steps in the Framework are performed correctly before Deploying the Fleet.

Development Integrity Assurance Team (DIAT) #

This team is made up of senior-level Code Engineers, Build Engineers, and Designers. They are responsible for reviewing every change before allowing it to be included in the DORC. They validate the work of the Quality Authority.

DevOps Usage & Compliance Head Engineer (DOUCHE) #

If the Right Way to do DevOps is not owned and controlled by an executive then nobody will do it. So, we need a named person to codify the Right Way in the DevOps Process Binder and hold all teams accountable to the DevOps Process Excellence Assessment. By staffing this role we prevent process drift and eventual mutation of the Right Way and can track our annual progress towards SADMF Maturity.

Enterprise Architecture Review Board (EARB) #

The EARB is responsible for maintaining the Book of Names. This master list defines all acceptable words and word combinations that may be used for naming things during coding. This ensures that Code Engineers will not be confused when they join a new Feature Team for the next Convoy. The EARB will meet every 6 weeks to review and reject any new words submitted for inclusion.

Feature Captain (FC) #

The mid-level manager who is responsible for tracking the progress of the feature they are assigned to.

Feature Team (FT) #

The Feature Team is the group of Code Engineers assembled to build a new feature for the next Convoy. Because we work so diligently to Build Quality In with the Tribunal, these teams should be able to deliver at maximum throughput as soon as they are formed.

Quality Authority (QA) #

Verifying quality is a specialist field that no Code Engineer is qualified to perform. In addition, performing testing impedes the ability of the Code Engineer to do their only job, type code. The Quality Authority team is the final arbiter of what the requirements mean and will create, maintain, and manually execute test scripts based on their understanding of the requirements. The end-user uses the system manually, so that is the only TRUE way to test it!

Review Board Review Board (RBRB) #

The RBRB is responsible for reviewing the work of the Enterprise Architecture Review Board and the Change Rejection or Acceptance Party. The RBRB will meet every 3 weeks to review and reject any decisions made by the EARB and CRAP. The members of the RBRB must come from areas as far removed from the work as possible to maintain objectivity.

Source Management Team (SMT) #

To improve Code Engineer productivity by reducing the work required to integrate changes, we introduce the Source Management Team. The SMT is responsible for authorizing new feature branches, creating the branches, and merging the complete branches from each Code Engineer into the Conflict Arbitration branch. They will then resolve all conflicts for the Code Engineers before alerting the Quality Authority that the Convoy is ready for testing.

System of Authority (SOA) #

This is the team of teams accountable for implanting SADMF in your organization. The SOA is staffed by contractors and consultants with diverse points of view. These principled practitioners will focus on implementing the orders of the ATO and will focus on updating plans, collecting metrics, assessing, and becoming trusted advisors for the teams so they can report the ground-level truth to leadership during the tribunal.

System of Service (SOS) #

This is the team of teams accountable for achieving deadlines and shipping code. The SOS will look to the chain of command for servant leadership to ensure self-governance and instruct the Feature Teams on their day-to-day work. The SOS is empowered to predictably deliver on time and on budget.

Unit Tester (UT) #

Code Engineers should be focusing on writing code. Testing is the job of specialists! The Unit Tester role is dedicated to writing unit tests for Code Engineers after the code is delivered to ensure the code works.