The following user story has been written: As a paying hotel guest I want to see the charges that have been added to my bill So that I can monitor my…

The user story provided is quite broad and encompasses multiple functionalities, which suggests it is

more of an epic than a small, deliverable user story. The INVEST criteria for Agile user stories require

that stories be Independent, Negotiable, Valuable, Estimable, Small, and Testable. In this case:

Independent: This user story seems to have dependencies, as the ability to print the bill, view it in

different currencies, and flag items are likely interconnected functionalities.

Negotiable: The user story provides specific solutions rather than outlining the problem to solve,

which limits the negotiation on how to implement the solutions.

Valuable: The story does provide value to the hotel guest, which is clear.

Estimable: With the information provided, the development team can likely estimate the effort

required.

Small: The story is not small; it covers multiple features that probably cannot be delivered in a single

iteration.

Testable: The acceptance criteria are testable, although they are quite detailed and prescriptive.

Reference = The explanation is based on the INVEST criteria as described in Agile

methodologies1234. The criteria are used to assess the quality of a user story, ensuring it is well-

defined and suitable for Agile development practices. The user story in question does not fully meet

the ‘Negotiable’ and ‘Small’ criteria, which is essential for maintaining flexibility and delivering

incremental value in Agile projects.