An Issue that was discovered in the Pre-Shipping environment that requires development work

Catastrophic issue identified - Severe impact, contain breaking workflow/data loss, zero-day/critical security vulnerabilities No workaround and should be fixed as an immediate priority Need to be released as a patch during regular milestone cycle as soon as a fix is available

Major issue identified - High impact, might contain breaking workflow/data loss, critical/high security vulnerabilities There is a workaround that exists but should be fixed as the next priority Might need to be released as a patch during regular milestone cycle/N+1 milestone release

Minor issue identified - Low impact, no breaking workflow/any workflow, medium/low security vulnerabilities There is a workaround that exists Can be released in N+1 or more milestone releases

Serious issue identified - Medium impact, no breaking workflow/no data loss, high/medium security vulnerabilities There is a workaround that exists and should be fixed after high priority Can be released in N+1 milestone release

This is a Process Concern

This is an item that is carried over from the R2 implementation to R3.

Any issues that need discovery / evaluation to get team to starting point, will be part of this title

This question focus on issues that affect the team velocity or satisfaction. It is important to be factual, not judgmental in the definition.

This question is intended to highlight things we learned along the way. Like "what went well", it is important to acknowledge and perhaps double down on learnings.

This question highlights gaps in our understanding.

Capture what went well in the project. Retrospectives often focus on pain; however, it is important to acknowledge positives or these might get lost in the future.