Comprehensive and Detailed Explanation From Exact Extract:
A core principle of Agile is frequent collaboration with stakeholders to ensure that the evolving solution continues to meet current and changing needs. Regular communication between Agile teams and stakeholders allows feedback to be incorporated frequently, so the product can be adjusted based on new information, shifting priorities, or clarified requirements.
This ongoing interaction ensures that:
The solution remains aligned with business value and user needs.
Requirements can evolve and be refined as the project progresses.
Misunderstandings are caught early, reducing rework and waste.
Therefore, the primary purpose is to confirm that the solution aligns with evolving requirements throughout the project.
Why the other options are incorrect:
A. To define and enforce a fixed set of project requirements from the start – This reflects a traditional, plan-driven (waterfall) mindset; Agile specifically embraces changing requirements.
B. To distribute tasks evenly and ensure team workloads are balanced – Task distribution is an internal team concern and is not the main reason for stakeholder communication.
D. To finalize documentation and lock project details early in development – Agile prioritizes working software and flexibility, not early lock-in of documentation and details.
[Reference:Information Technology Management Study Guide – Agile Principles: Customer Collaboration and Responding to Change., , , ]
