@@ -52,6 +52,12 @@ Here's the process to follow to create a new Data issue:
4. Leave the **Assignees** blank. The Data Team will process your request as a part of our [Daily Triage](/handbook/enterprise-data/how-we-work/triage/).
<!--need to review the activities that are part of triage process -->
### Backlog Grooming
Backlog grooming is the ongoing process of reviewing and cleaning up the backlog to keep it healthy and actionable. Regular grooming ensures we're focused on work that still provides business value. This is the collective responsibility of all members of the Data team. Team members should regularly review issues that are assigned to them / that they have created and close items that are no longer needed, have been superseded, are stale (not touched in 365 days with no active business need), or lack sufficient detail. Closing an item doesn't discard the work, if priorities change we can reopen it. Use your judgment and consult your manager or stakeholder when uncertain. Grooming happens throughout the year.
**Note:** An [automated triage policy](/handbook/enterprise-data/how-we-work/triage/#stale-issue-management) will automatically close issues that have not been modified for 365 days. The bot checks for any (technical) modifications in an issue, so actions like linking to an issue count as an update and will prevent closure.
### Backlog Management and Prioritization
The Data Team backlog consists of all issues that the Data team could work on, but have not yet started development work on. This includes issues in the `workflow::2 - waiting for prioritization`, `workflow::3 - refinement`, and `workflow::4 - ready to develop` stages. These issues have been validated during triage and determined to warrant development.
