Architecture as Code · Module 5 · Organisation & Leadership

Team Structure and Competency Development for IaC

The lesson designs the operating model for Architecture as Code teams. It covers platform teams as internal service providers, the competency domains of specialists, a skills matrix with four technical levels and interpersonal skills, structured learning programmes, agile team models that treat infrastructure as a product, platform and product team charters, communities of practice, and balanced scorecards for performance and career progression.

Lesson 22 of 31Chapter 1860 minutes

Read the chapterThe whitepaperThe slides

All courses / Architecture as Code / Module 5 / Chapter 18

Learning objectives

After the lesson the participant can:

Key concepts

Platform team
An internal service provider that owns the common toolchains, guardrails and reusable modules which let application teams move quickly without sacrificing governance, balancing central expertise with decentralised autonomy.
Skills matrix
A shared view of expectations at four levels: Foundation (basic operations), Practitioner (infrastructure automation), Advanced (architecture design) and Expert (platform leadership), complemented by communication and leadership skills and revisited in quarterly development conversations.
Infrastructure as a product
A team model in which cross-functional teams work from a prioritised backlog, product owners represent internal customers, and service level objectives, error budgets and deployment frequency tie platform work to business value.
Community of practice
A structure that connects practitioners across product lines with defined roles, cadences and collaboration platforms, so that insights from talks and workshops reach documentation, reusable modules and the operating model.
Balanced scorecard
A performance view that combines operational indicators drawn from the DORA software delivery metrics with contributions to knowledge sharing and cross-team collaboration, supporting career progression for specialists.

Interactive exercises

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

Interactive exercise 1 · Sort

Competencies by level of mastery

Sort each competency into the level of the technical skills matrix where the chapter lists it.

Interactive exercise 2 · Match

Elements of the operating model

Match each element of the operating model to its function in the chapter.

Teaching plan

10 minTeacher presents why traditional organisation charts hinder the practice and how platform teams and product-aligned delivery teams divide the work.
15 minParticipants rate themselves or their team privately against the technical skills matrix, then discuss in pairs which level transitions are hardest.
10 minTeacher covers learning programmes, agile team models, the charter and the community of practice framework.
20 minExercise: write a platform team charter and a community of practice outline.
5 minClose on the balanced scorecard and what it rewards beyond delivery numbers.

Discussion

  1. What would have to change in how your platform team is funded and measured for it to act as a service provider with internal customers?
  2. The Expert level of the skills matrix is defined by mentoring, tool selection and roadmaps more than by technical depth. What does that say about how seniority should be recognised?
  3. How can a manager track completion of training while still placing the emphasis on practical demonstration, as the chapter asks?

Written exercise

Exercise · 20 minutes

A platform team charter and a community of practice

Write a charter for a platform team in your own organisation, in structured form. State its mission, the internal customers it serves, what it owns (toolchains, guardrails, reusable modules), what the product teams own, two service level objectives, and three measures that tie its work to business value, drawing on deployment frequency, error budgets or adoption. State how often the charter is reviewed, following the chapter's quarterly alignment reviews. Then outline a community of practice that connects the platform team with product teams: its coordinator role, its meeting cadence, its channels, and two success criteria that show knowledge reaches documentation and reusable modules.

Deliverable: A structured team charter of about one page and a half-page community of practice outline with roles, cadence and success criteria.

Self-test

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

  1. Which focus area does the skills matrix assign to the Practitioner level (Level 2)?

    Show the answer

    C. Infrastructure automation
    The four levels are Foundation (basic operations), Practitioner (infrastructure automation), Advanced (architecture design) and Expert (platform leadership).

  2. What do platform teams own, according to the chapter?

    Show the answer

    A. The common toolchains, guardrails and reusable modules
    Platform teams act as internal service providers and own the common toolchains, guardrails and reusable modules that let application teams move quickly without sacrificing governance.

  3. What do the balanced scorecards in the chapter combine?

    Show the answer

    D. DORA-based operational indicators with knowledge-sharing contributions
    Balanced scorecards combine operational indicators drawn from the DORA software delivery metrics with knowledge-sharing and cross-team collaboration contributions.