Agile governance conversations should focus primarily on:

Question

Options

• AReports
• BDeviations
• CTrade-offs
• DEscalations

• A
  6% (2)
• B
  3% (1)
• C
  75% (24)
• D
  16% (5)

Explanation

Agile governance centers on trade-offs because Agile teams constantly balance competing priorities - speed vs. quality, scope vs. cost, technical debt vs. delivery - and governance conversations exist to make those value-based decisions transparent and aligned with organizational goals.

Why the distractors are wrong:

• A. Reports - Reports are artifacts, not conversations. Agile governance avoids heavy documentation culture; reporting is an output, not the focus.
• B. Deviations - Deviations from plan are a traditional/waterfall concern. Agile embraces change, so "deviation" framing conflicts with the Agile mindset.
• D. Escalations - Escalations are exception-handling mechanisms, not the primary purpose. Healthy Agile governance reduces the need for escalations by surfacing trade-offs early.

Memory tip: Think of Agile governance as a steering wheel, not a report card. You're constantly making directional trade-off decisions (go faster vs. go safer, do X vs. Y) - not just measuring variance from a plan.

No community discussion yet for this question.