(Select 2) Why is Architectural Runway important?

Question

Options

• AIt supports a stable velocity.
• BIt provides the documentation on which Features and Capabilities are built.
• CIt iteratively evolves the architecture to meet changing needs.
• DIt allows for nontechnical changes

• A
  88% (15)
• B
  6% (1)
• D
  6% (1)

Explanation

Architectural Runway is the existing code, components, and technical infrastructure needed to implement near-term features without excessive redesign - and both A and C capture its core value. It supports stable velocity (A) because teams aren't constantly blocked by missing infrastructure or forced into costly rework before they can deliver; the runway lets them move at a consistent, predictable pace. It iteratively evolves the architecture (C) because runway isn't built once and frozen - it's continuously extended in each iteration to stay ahead of emerging business needs.

Why B is wrong: Architectural Runway is not about documentation - it's about actual, working technical infrastructure. Features and Capabilities are built on top of the runway, not on documentation.

Why D is wrong: Runway is explicitly a technical concept. It has no bearing on nontechnical changes; that conflates architectural work with general change management.

Memory tip: Think of Architectural Runway like a runway at an airport - planes (Features) need it to take off consistently (stable velocity), and you keep extending it as more flights are planned (iteratively evolves). No documentation or nontechnical work gets planes in the air.

No community discussion yet for this question.