(Select 3) You are invited to help a program where, even though not mandated by the external environment, management requires teams to make big, up-front, and detailed scope commitments for every…

Question

Options

• AIllustrate the power of feedback in content decision-making.
• BEmphasize the value of "Responding to change" from the Agile Manifesto.
• CExplain that too much up-front detail demotivates Product Owners as they have almost nothing to
• DExplain the "understand and exploit variability" principle or product development flow.
• EExplain why development doesn't need to commit to anything in Agile.

• A
  58% (21)
• C
  14% (5)
• E
  28% (10)

Explanation

Options A, B, and D are correct because they address the root problem: management is locking in scope too early, which contradicts core Agile and Lean principles. A (feedback loops) shows decision-makers that content decisions improve when informed by real data rather than up-front guesses. B directly cites the Agile Manifesto's second value - "Responding to change over following a plan" - giving the coaching a credible, canonical foundation. D (Donald Reinertsen's principle of exploiting variability) explains why rigid up-front commitments are economically harmful: variability in product development is an asset to be leveraged through options, not eliminated through premature lock-in.

C is wrong because it misidentifies who is demotivated - it's typically developers and teams who are demotivated by over-specified scope, not Product Owners; the framing is also vague and unlikely to persuade management. E is wrong because it's a false and extreme claim - Agile teams absolutely commit, just to iteration-level goals and outcomes, not to a fixed big-bang scope; saying "development doesn't need to commit to anything" would undermine trust and misrepresent Agile entirely.

Memory tip: Think "FCV" - Feedback, Change-value, Variability - the three legitimate levers for coaching against big up-front commitments. Any answer that distorts or exaggerates Agile (like E) or misattributes the problem (like C) is a trap.

No community discussion yet for this question.