An agile project leader notices that the team's velocity has decreased. In examining data provided by team members, the project leader discovers that one team member has been slow to enter story statu

Question

Options

• AThe team will be unable to understand the iteration's status
• BThe team will be unable to judge the project design's validity
• CThe team cannot give accurate updates to management
• DTeam collaboration cannot be measured effectively

• A
  71% (34)
• B
  10% (5)
• C
  15% (7)
• D
  4% (2)

Explanation

Story status updates are the primary mechanism by which a team tracks what is done, in progress, and remaining within an iteration. When a team member delays entering statuses, the information radiator (e.g., sprint board, burndown chart) reflects inaccurate data, making it impossible for the team to understand where they truly are in the iteration (A). While this could indirectly affect management reporting (C) or collaboration (D), the most immediate and direct consequence is loss of iteration status visibility. Design validity (B) is unrelated to story status tracking. Accurate, timely status updates are a fundamental agile transparency practice.

No community discussion yet for this question.