If the Right Way to do DevOps is not owned and controlled by a single senior manager, 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 attempts process drift and eventual mutation of the Right Way.
The Feature Team is the group of Coders who are 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.
To improve Coder productivity by reducing the work required for integrating 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 Coder into the Conflict Arbitration branch. They will then resolve all conflicts for the Coders before alerting the Quality Control team that the Convoy is ready for testing.
Coders are too close to the problem to effectively review code for their Feature Team. Additional, reviewing code takes time away from coding. To resolve this, the CSET is formed to perform all code reviews. The CSET is also responsible for defining and enforcing all coding standards for the enterprise. This includes, but is not limit to:
Verifying quality is a specialist field that no Coder is qualified to perform. In addition, performing testing impedes the ability for the Coder to do their job, write code. The Quality Authority team is the final arbiter of what the requirements mean and will create, maintain, and manually execute tests 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!
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 Coders 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.
The DMRB is responsible for reviewing all of the documentation contained in the Convoy Manifest to ensure all Scaled Agile DevOps processes were followed to the letter before allowing the convoy to sail. This is a crucial step to assure our customers we are as SAD as possible. This board consists of representatives carefully chosen from areas unrelated to any feature so they can have the utmost objectivity.