Anti-Patterns in Architecture as Code Programmes

All courses / Architecture as Code / Module 7 / Chapter 26B

Learning objectives

After the lesson the participant can:

• Identify anti-patterns from the six clusters in a described programme.
• Match each anti-pattern to the recovery the chapter recommends.
• Use the four leading indicators to detect anti-patterns early.
• Classify an anti-pattern by severity and plan a remediation with the three-step playbook.

Key concepts

Treating AaC as a tool purchase

A strategic anti-pattern in which budgets focus on licences and consultants while change management, governance design and capability building are neglected. Recovery: treat the practice as a product with a roadmap, a coaching budget and a guild that curates shared models.

Audit theatre

Staging elaborate compliance demonstrations just before regulatory reviews, with hand-crafted dashboards and manually executed scripts. Recovery: generate policy evidence automatically in pipelines so auditors can review the repository.

Fork-first module evolution

Teams copy shared modules instead of contributing improvements upstream, leaving dozens of subtly different variants that cannot be upgraded. Recovery: contribution agreements, automatic surfacing of module drift and mentoring through upstream pull requests.

Leading indicators of anti-patterns

Four early signals: repository contribution imbalance, exception backlog growth, pipeline failure clustering and shadow tooling proliferation.

Remediation playbook and severity

Three steps: diagnose the root cause without blame, run a corrective experiment with success metrics, share the learning and watch for regression. Severity is Critical, High, Medium or Low, each with a recommended response.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Teaching plan

Discussion

1. The chapter describes how a central team responds to bypassing with more rigid controls, which accelerates fragmentation. How can that loop be broken?
2. Why does the chapter treat hero culture as a risk to the programme and not as a sign of commitment by the people concerned?
3. Which of the four leading indicators could you measure in your repositories this week, and what would you expect to find?

Written exercise

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

1. What recovery does the chapter give for policy drift through manual exceptions?

   1. Move the exception list from spreadsheets to a shared wiki page
   2. Store time-boxed exceptions as code and evaluate them with the same policy engine
   3. Forbid all exceptions and escalate every request to the board
   4. Reconcile the exception spreadsheets and email threads by hand before each regulatory audit
   Show the answer

   B. Store time-boxed exceptions as code and evaluate them with the same policy engine
   Exceptions are stored as time-boxed code and evaluated with the same policy engine as the rules they relax, so they surface automatically in pipelines until the owning team resolves them.

2. A small minority of contributors performs the majority of merges. Which leading indicator is this, and what does it suggest?

   1. Pipeline failure clustering, suggesting automation fatigue
   2. Exception backlog growth, suggesting governance drift
   3. Shadow tooling proliferation, suggesting trust gaps
   4. Repository contribution imbalance, suggesting gatekeeping or insufficient coaching
   Show the answer

   D. Repository contribution imbalance, suggesting gatekeeping or insufficient coaching
   Repository contribution imbalance, a small minority performing the majority of merges, suggests gatekeeping or insufficient coaching.

3. According to the severity table, what is the recommended response to a Critical anti-pattern?

   1. Escalate to leadership, pause scaling and address it within the sprint
   2. Add it to the backlog and address it within the quarter
   3. Monitor it and document it in the risk register
   4. Prioritise it in the next planning cycle and assign an owner
   Show the answer

   A. Escalate to leadership, pause scaling and address it within the sprint
   A Critical anti-pattern is actively blocking delivery or causing security incidents; the response is to escalate to leadership, pause scaling and address it within the sprint.