Wiki » History » Version 7
Redmine Admin, 02/02/2023 01:00 AM
| 1 | 1 | Redmine Admin | h1. Wiki |
|---|---|---|---|
| 2 | 4 | Redmine Admin | |
| 3 | 2 | Redmine Admin | h2. Backlog Operations |
| 4 | 3 | Redmine Admin | |
| 5 | 2 | Redmine Admin | This page outlines information relevant to the backlog and the generation of tasks. |
| 6 | |||
| 7 | Covered Topics: |
||
| 8 | * What is a backlog and it's purpose |
||
| 9 | * How to organize a backlog |
||
| 10 | * Hierarchy of the backlog |
||
| 11 | * How to create a story |
||
| 12 | * How to create a task |
||
| 13 | * How to parent a story |
||
| 14 | * Why and when should I add a story to the backlog? |
||
| 15 | 5 | Redmine Admin | * Updating the backlog |
| 16 | |||
| 17 | 6 | Redmine Admin | h2. What is a Backlog and its purpose |
| 18 | 7 | Redmine Admin | |
| 19 | 6 | Redmine Admin | *Definition* : A product backlog is a prioritized list of work for the development team that is derived from the roadmap and its requirements. The most important items are shown at the top of the product backlog so the team knows what to deliver first. |
| 20 | |||
| 21 | *It's purpose* : It's a reliable and sharable outline of the work items for a project. |
||
| 22 | |||
| 23 | Fostering discussion around what's important gets everyone's priorities in sync. These discussions foster a culture of group prioritization ensuring everyone shares the same mindset on the program. |
||
| 24 | |||
| 25 | The product backlog also serves as the foundation for iteration planning. All work items should be included in the backlog: user stories, bugs, design changes, technical debt, customer requests, action items from the retrospective, etc. This ensures everyone's work items are included in the overall discussion for each iteration. Team members can then make trade-offs with the product owner before starting an iteration with complete knowledge of everything that needs to be done. |
||
| 26 | |||
| 27 | 5 | Redmine Admin | [[Sprint_Operations]] |