How are user inputs FIRST gathered in the 'quality' practice?

Question

Options

• AAs user stories in the product backlog
• BAs epic user stories in the project backlog
• CAs the project Definition of Done in the quality management approach
• DAs a quality control activity in the quality register

• A
  86% (25)
• B
  3% (1)
• C
  7% (2)
• D
  3% (1)

Explanation

User inputs are initially gathered as user stories in the product backlog in PRINCE2 Agile. User stories represent small, customer-focused requirements that capture the "who," "what," and "why" of a feature. These stories form the foundation of requirements and quality criteria for the product and ensure that development is driven by user needs and value delivery. The Definition of Done is developed later as part of the quality management approach to specify when work is complete. Epic user stories are larger features that can be broken down into smaller user stories. The quality register tracks quality-related activities but is not the first step for gathering user inputs.

No community discussion yet for this question.