In Agile practices, what is the purpose of User Stories?

User Stories serve the primary purpose of expressing user needs and intended outcomes in Agile practices, making option C the correct choice. They are crucial elements in understanding what the user wants from a product or feature. By focusing on the perspective of the user, User Stories provide context and clarity around the desired functionality, helping teams prioritize and align their development efforts with user value.

This user-centric approach allows teams to capture requirements in a succinct manner, typically following a format that specifies who the user is, what they need, and why that need is important. For example, a User Story might read: "As a [type of user], I want [an action] so that [a benefit]."

This focus not only promotes collaboration among stakeholders but also helps ensure the development work is meaningful and directed towards achieving specific outcomes that improve user satisfaction. This clarity strengthens the team's ability to deliver working software incrementally, as they can assess their progress based on whether these user needs are being met.

In contrast, the other options do not align with the fundamental purpose of User Stories in the Agile framework. They either focus on aspects that are unrelated to capturing user perspectives or represent different aspects of project management and tracking. Understanding this core purpose of User Stories is essential for effective