Engineering standards
Standards written into the repository, and a score that tracks progress
The AIUBY team works with yours to map the engineering inventory, design the architecture blueprint, write the standards and measure each round with a score. Standards and blueprint land in your repository through a pull request, reviewed by the code owners.
The organization's signed-in area holds the inventory, the blueprint, per-squad indicators and the score with its history, always stamped with when the team published the reading.
How it works
- An inventory of what exists in engineering: installed items, items new in the round and reusable standards.
- An architecture blueprint with the status of each item, published with the round.
- An engineering score from 0 to 100, with a level, weekly history and a comparison with the starting point.
- Per-squad indicators in the same publication, so teams are compared on the same yardstick.
- Only the published round is visible to the organization: team drafts never reach the screen.
- Every change to the repository goes in through a pull request that your team reviews and merges.
Example use case
A company with five squads keeps its engineering standards in a wiki that each team reads differently. The AIUBY team maps the inventory, writes the blueprint and standards into the repository through a pull request and publishes the first score. Each round, leadership opens the signed-in area, compares the score with the starting point and sees which squad has not adopted the standard.
What it does not do
- It is not self-service: the AIUBY team runs the assessment and publishes each round.
- The score is not recalculated automatically on every commit; it changes when a new round is published.
- It is not purchased through the account: the work is an engineering service, arranged with the team.