Agile architecture

Question 1

What problem does “agile architecture” aim to solve?

Answer 1

Balancing the need for a coherent long-term structure with the fast, iterative change cycles of agile delivery. :contentReference[oaicite:27]{index=27}

Question 2

Define intentional vs. emerging architecture.

Answer 2

Intentional = structure planned up-front by architects; Emerging = structure that crystallises from sprint-level decisions. Agile architecture seeks the sweet spot between them. :contentReference[oaicite:28]{index=28}

Question 3

What is an “architectural runway” in SAFe terms?

Answer 3

A visible backlog of architectural enablers that must exist ahead of upcoming features so teams can develop safely at speed. :contentReference[oaicite:29]{index=29}

Question 4

Differentiate “feature” stories from “enabler” stories.

Answer 4

Features deliver end-user value; Enablers implement cross-cutting infrastructure or quality work that supports future features. :contentReference[oaicite:30]{index=30}

Question 5

Name the three structural lenses used to reason about agile architecture.

Answer 5

System architecture, development organisation, and production infrastructure. :contentReference[oaicite:31]{index=31}

Question 6

How does Conway’s Law affect agile architecture?

Answer 6

Code structure tends to mirror team communication paths; architects must consider org design when shaping services or modules. :contentReference[oaicite:32]{index=32}

Question 7

List three quality attributes that become especially critical in agile contexts.

Answer 7

Modifiability, interoperability, and time-to-market. :contentReference[oaicite:33]{index=33}

Question 8

In Scrum, who is formally responsible for architecture?

Answer 8

No dedicated role; design emerges within the team, though an experienced member often acts informally as steward. :contentReference[oaicite:34]{index=34}

Question 9

How does SAFe re-introduce architectural roles?

Answer 9

It defines System, Solution, and Enterprise Architects who own the runway and coordinate cross-team enablers. :contentReference[oaicite:35]{index=35}

Question 10

Explain horizontal vs. vertical decomposition of enabler work.

Answer 10

Horizontal: each feature team builds its own scaffolding; Vertical: a dedicated platform team supplies shared services; many orgs start horizontal then shift vertical. :contentReference[oaicite:36]{index=36}

Question 11

What KPI trio is often tracked to gauge socio-technical health?

Answer 11

Deployment frequency, lead time from merge to prod, and defect escape rate. :contentReference[oaicite:37]{index=37}

Question 12

Give one reason “big-up-front” architecture fails in agile settings.

Answer 12

Requirements and priorities shift sprint by sprint, making heavy early designs obsolete before implementation. :contentReference[oaicite:38]{index=38}

Question 13

Describe a practical routine for managing the runway.

Answer 13

Surface enabler stories, align them a few sprints ahead of features, review runway length each PI, schedule refactoring spikes when velocity catches up. :contentReference[oaicite:39]{index=39}

Question 14

What is the danger of having only emerging architecture?

Answer 14

Codebase drifts into a patchwork of one-off hacks, hurting long-term quality attributes like performance and security. :contentReference[oaicite:40]{index=40}

Question 15

Why are DevOps pipelines considered part of architecture in agile?

Answer 15

Deployment automation shapes feedback loops and therefore influences how quickly design changes can be validated. :contentReference[oaicite:41]{index=41}

Question 16

Give an example of an architectural enabler in a marketplace project.

Answer 16

Implementing a structured-logging backbone before shipping buyer/seller features. :contentReference[oaicite:42]{index=42}

Question 17

How can architects safeguard conceptual integrity when dozens of teams sprint independently?

Answer 17

Set and evangelise lightweight guardrails—naming conventions, API style guides, shared libraries—monitored through CI linting. :contentReference[oaicite:43]{index=43}

Question 18

What metric signals that the runway is shrinking too fast?

Answer 18

Feature velocity exceeds enabler throughput, causing blockers or quality regressions in upcoming sprints. :contentReference[oaicite:44]{index=44}

Question 19

Name two agile practices that support emergent architecture without chaos.

Answer 19

Refactoring as first-class work and automated regression testing. :contentReference[oaicite:45]{index=45}

Question 20

How does vertical decomposition affect team autonomy?

Answer 20

It frees feature teams from infrastructure chores but introduces a dependency on the platform team’s backlog and cadence. :contentReference[oaicite:46]{index=46}

Question 21

State one guideline for time-boxing architectural spikes.

Answer 21

Keep spikes short (one sprint or less), define a clear hypothesis, and produce a recommendation, not production code. :contentReference[oaicite:47]{index=47}

Question 22

Why is modifiability often the top ASR in agile programmes?

Answer 22

Frequent requirement changes demand low cost of code alterations and rapid redeployment. :contentReference[oaicite:48]{index=48}

Question 23

In Kanban, where does architecture planning typically sit?

Answer 23

As work items in the same flow lane, prioritised alongside features; WIP limits force explicit trade-offs between enabler and feature tasks. :contentReference[oaicite:49]{index=49}

Question 24

Complete the sentence: “An agile architect’s role is more ___ than ___.”

Answer 24

Steward than dictator—guiding patterns and principles rather than issuing rigid designs. :contentReference[oaicite:50]{index=50}

Question 25

What practical checklist can guard against over-engineering the runway?

Answer 25

Ask: (1) Does an upcoming feature depend on this enabler? (2) Is there a cheaper experiment? (3) Can we defer until feedback proves need? :contentReference[oaicite:51]{index=51}

Question 26

Provide a concise exam definition of agile architecture.

Answer 26

The practice of supplying just-enough intentional structure, via an architectural runway of enablers, to let agile teams evolve a system rapidly without sacrificing long-term qualities. :contentReference[oaicite:52]{index=52}