Skip to content

Retro 29.2 Manage Retro Outputs Effectively #1591

@HimaniTanwarGov

Description

@HimaniTanwarGov

Description:
Retro action items are turning into an unmanaged “idea backlog” with limited follow-through. We need a structured way to track, prioritize, and close them.

Next Steps:

  • Limit retro action items to 1–2 per sprint
  • Assign a clear owner for each action item
  • Track them on the zenhub board for visibility
  • Review progress in stand-ups or mid-sprint check-ins
  • Set up a dedicated session to review past retro items, close irrelevant ones, and prioritize the remaining
  • Revisit and close items in the following retro

Metadata

Metadata

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions