In Agile project management, what is a user story and what is its primary purpose?

Correct answer: A description of a feature from end-user perspective that defines requirements for a sprint

In Agile, a user story is a short, informal description of a desired feature written from the perspective of an end user, typically following the format 'As a [role], I want [feature], so that [benefit]'; its primary purpose is to capture requirements in a user-centric way that fits within a sprint and drives prioritized backlog items. Option B is incorrect because the project charter is a formal project management document that authorizes the project and is not related to individual feature descriptions in Agile. Option C is incorrect because meeting notes or minutes are administrative records of discussions and decisions, not requirement artifacts. Option D is incorrect because a project history narrative describes the evolution of the project over time, which is a retrospective document, not an Agile requirements tool.