Backlog refinement issues

Blocked by some other issue

Issues that require communication about the features that are being deprecated.

Backlog issues that are ready for the "Backlog Refinement" meeting but not yet ready for the sprint. The issue is missing what and how, and why.

issue related specifically to ops without need for dev code changes

Top priority issues that should be brought in to the current sprint and worked on before any other issues

High priority issues that should be moved in to the next sprint and worked on first

Standard priority issues. Average work items that contribute to the current sprint goals but are not mission critical

Low priority issues. Can be pulled in to the sprint as needed, nice to haves.

issues that are ready to be brought in to the current or next sprint

issues that have been inactive in the backlog for greater than 60 days that need to be reviewed again to determine if they are still relevant to our current goals

Issue that we should test on production candidates before roll out to production

A Scrum Spike is a time-boxed research or exploratory task undertaken by the development team to reduce uncertainty and gain knowledge before committing to building a feature or solution