A team finishes developing all of their Stories in the first six days of the Iteration, tests them in the following two days, and fixes bugs in the days remaining. How is the team behaving?

Question

Options

• AThey are abusing the practice of hardening
• BThey are ignoring nonfunctional requirements within the Iteration
• CThey are waterfalling the Iteration
• DThey are applying the Agile development practice of "separation of concerns"

• A
  15% (4)
• B
  12% (3)
• C
  69% (18)
• D
  4% (1)

Explanation

Completing all development first, then testing, then fixing bugs mirrors the sequential phases of a Waterfall model - just compressed into a single Iteration, which defeats the purpose of iterative, integrated Agile delivery where work flows continuously and stories are developed and tested together. A is wrong because hardening is a SAFe concept (a hardening Sprint for stabilization), not something being abused here - there's no mention of a dedicated hardening period. B is wrong because nonfunctional requirements (performance, security, etc.) aren't mentioned as missing; the issue is the sequential workflow, not the type of work. D is wrong because "separation of concerns" is a software design principle about modularity, not an Agile team practice describing how work is sequenced across days.

Memory tip: Think "mini-Waterfall" - if a team within an Iteration does all dev → all test → all fix as distinct phases, they've just shrunk a Waterfall into two weeks. Agile demands these activities overlap and integrate within each Story, not after all Stories are "done."

No community discussion yet for this question.