A well-written user story in the Disciplined Agile (DA) framework describes the product requirements from the customer's perspective. In DA, a user story is a short, simple description of a feature told from the perspective of the person who desires the new capability, typically a user or customer of the system. The primary purpose of a user story is to articulate how a piece of work will deliver a particular value back to the customer.

A user story should focus on what the customer needs and wants, rather than a fixed outcome (A), the needs of all users (B), or merely the expectations of the product owner (C). It shouldcapture the customer's perspective (D) to ensure the team understands who the end-user is, what they need, and why they need it. This customer-centric approach helps the team create value-driven features and maintain alignment with customer expectations.

Disciplined Agile emphasizes that user stories are part of a collaborative conversation with the stakeholders, which allows the team to explore and understand the customers' needs effectively. The DA framework encourages iterative development based on customer feedback, ensuring that each user story is aligned with delivering maximum customer value.