A Business Analyst (BA) noticed that one of the User Story Card files for the project indicated that it had recently been modified. The BA wanted to…

A User Story Card, when used as a formal project artifact or requirements document, typically follows standard document control procedures. A "Document Control" or "Amendment History" section is the standard location for tracking changes. This section serves as a change log, detailing the version, date, author, and a description of the modifications made to the document. This directly provides the "who, what, and why" information the Business Analyst is seeking regarding the recent changes.

A. File properties may show who last saved the file but will not provide details on what was changed or the reason for the change.

B. The Action Items tab is for tracking tasks related to the story's implementation, not for logging changes to the story document itself.

D. The UI Fields tab contains the requirements related to user interface elements; it is part of the story's content, not its change history.

1. Guidewire SurePath Agile Methodology Guide, "Project Artifacts and Templates," Section 3.4, describes the standard structure for requirements documents, including a document control section for versioning and amendment history.

2. (General Academic Reference) Sommerville, I. (2011). Software Engineering (9th ed.). Pearson. Chapter 4, "Requirements Engineering," discusses the importance of requirements traceability and change management, often implemented via history sections in requirements documents.