The Backlog holds all your work to be done until the end of the project
Organize your work to be done in a structured way.
The backlog is a structured approach to list everything that is relevant for your project/product. It is the source of all requirements. It represents the dynamic and agile plan of your project. It contains everything that is required to develop your product, but it is still open and changeable.
A backlog entry is called a story. In order to stay open and changeable ensure your backlog is short and future stories are not too detailed right from the start. Only stories that are relevant for the next sprints should be ready to get estimated.
A backlog is prioritized. The most detailed and important stories are on the top of your backlog. This way the product owner ensures that the stories with the highest value for the product are done first and you can achieve an early ROI.
SCRUM and Kanban Projects
Expect several hours a week to refine and work on your backlog
The biggest mistake a product owner can make is to write to detailed stories. It is very important that a story not only stays in a backlog because it was so much work to write it.
23/02/2020 08:35:58 - Fix spelling and MD issues Fixed a number of issues pointed out by mdlint. (Frank Meerkötter)
22/02/2020 22:22:11 - Finalize agile essentials for first release (Jeremias Bosch)
20/02/2020 10:35:56 - Initial commit agile essentials (Frank Meerkötter)