Part IV. Populating the product backlog
Once we know the overall goals of a project, we can examine the project in more detail and identify features. These features will go into our backlog, be prioritized, and be added to an iteration if they are of high value.
A product backlog holds features that tie to the product. These features could include bug fixes, product suggestions, refactoring work, nonfunctional requirements, migration work, or content setup.
For a one-time project the backlog is initially populated after team alignment. If you are doing steady-state releases, your backlog already exists and you are in a state of constantly reviewing it before proceeding with your next iteration or release.
Once you have a running backlog, anyone can ...
Get Becoming Agile now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
