A new agile team member notices that the team's current process involves excessive documentation. What should the new team member do?

Question

Options

• ABreak down the feature into smaller parts, and commit to completing the minimum viable product.
• BComplete the iteration to which they have already committed, and include the feature in the next
• CChange the planned features to include only the vitally important one.
• DExtend the iteration to complete the feature.

• A
  81% (22)
• B
  4% (1)
• C
  11% (3)
• D
  4% (1)

Explanation

Agile values 'working software over comprehensive documentation.' When excessive documentation is identified as waste, the right response is to focus on delivering a Minimum Viable Product (MVP) by breaking work into smaller, manageable pieces-eliminating unnecessary documentation overhead. This approach aligns with the agile principle of delivering incremental value rather than spending time on artifacts that do not directly contribute to the working product. Options B and D (extending or completing the full iteration scope) perpetuate the waste. Option C (changing planned features arbitrarily) does not address the documentation problem systematically. Breaking down work to focus on the MVP directly attacks the root issue of waste in the process.

No community discussion yet for this question.