Retro
- Probably good for young teams
- Mature teams generally have identified and productive already
Retro topics
- Style 1:
- What we should continue
- What we should stop
- What we should start
- Style 2:
- What went well
- What to improve
- Action Items
- Appreciation from people
Retro points
- Programming:
- KT from people
- Peer programming
- Design Sessions/Meetings
- Code Quality:
- PR reviews and internal reviews
- Writing tests and Code coverage
- Agile related:
- Grooming before we pickup the task
- Story points
- Good Jira description
- Time logging
- Productivity calculation
- Write retro points during the development itself instead of in a call
- Delivery related:
- Identify Dependencies
- Have clear goals what needs to be delivered
- Transparency on delivery needed
- Too many changes during sprint
- Fun:
- games monthly in Friday
- team outing