Final answer:
A user story should not discuss specific technologies as its purpose is to focus on customer value, not implementation details. Being technology-agnostic allows flexibility and avoids early poor design decisions.
Step-by-step explanation:
A user story is a fundamental tool in Agile software development, aimed at capturing a description of a software feature from an end-user perspective. The question asks which of the following a user story should not do.
Be written using language the customer understands
Be short
Discuss specific technologies
Describe one thing the software needs to do for the customer
The correct answer is that a user story should not discuss specific technologies. The purpose of a user story is to focus on the value or the outcome the feature will bring to the customer, rather than how the feature should be implemented. Mentioning specific technologies can limit the flexibility of the development team and potentially lead to poor design decisions. A user story should remain technology-agnostic to allow for the best technical solutions to emerge during the development process.