A key stakeholder cannot attend the project vision statement development workshop. The stakeholder has emailed their requirements to the agile team lead, and believes that the vision statement is not

Question

Options

• AEmphasize to the stakeholder that a common, detailed vision will better ensure team
• BPersonally meet with the stakeholder to understand their requirements, and then share the vision
• CWork with the team to create a vision from the stakeholder's supplied requirements.
• DExplain to the team that creating a vision is not critical in agile projects, as requirements may

• A
  79% (22)
• B
  11% (3)
• C
  7% (2)
• D
  4% (1)

Explanation

The project vision is a foundational alignment tool in agile - it ensures all team members and stakeholders share a common understanding of the goal. The agile team lead's first priority is to help the stakeholder understand why the vision matters and encourage their participation, rather than simply accommodating their absence. A shared vision reduces misalignment, miscommunication, and rework later. Option B (personal meeting) is a good secondary step but the key action is correcting the stakeholder's misconception first. Option C ignores the alignment problem. Option D actively harms the project by validating the false belief that vision is unimportant.

No community discussion yet for this question.