Product backlog
The first phase is to collect customer high-level requirements and prepare product backlog. Customer requirements are ordered based on their priority in a product backlog. These requirements are prioritized by the product owner. The product backlog includes all of the features that the customer expects in the final product. These requirements are termed user stories.
A user story provides details about the requirement from an end user perspective, focusing on what they want to do or what feature they want to have in a product. These user stories do not include the complete set of requirements—instead, they only include features that customers have in their mind at the time of starting a project. The customer expected feature ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access