The document discusses retrospectives in Agile development. A retrospective is a regular meeting where a team reflects on what went well and poorly in the previous sprint or milestone. The team identifies actions to improve effectiveness, such as removing pain points or increasing test coverage. A common retrospective template involves categorizing items as "GLAD, SAD, MAD" and assigning action items to improve identified issues.
2. What is Retrospective?
As Agile Manifesto says,
“At regular intervals, the team reflects on how to
become more effective, then tunes and adjusts its
behaviour accordingly.”
Retrospective is,
1. Time of reflection.
2. Identify ways to be more effective.
3. Remove pain points, if any.
3. Questions to ask:
What we did well?
What we did not do well?
What could be improved?
4. Retrospective template
GLAD SAD MAD ACTION ITEM
Client Involvement Test Coverage Definition of Done Owner - TestCoverage - Team
Code Cleanliness Daily Standup Timing
Owner - Standup
regularisation - Alan( Team
Member)
Better estimation Owner - Team
and so on….
