Abstract:
Retrospectives are a critical ceremony of agile development methodology and it's ironical that they are mostly ignored as well and teams keep on facing issues repetitively. While there are various creative ways of conducting retrospectives, there is very less emphasis on how to track findings of retrospectives and make it useful for a team.
Key Takeaways:
1. How to get the maximum benefit from retrospectives?
2. What are ways via which action items from retrospectives can be tracked?
3. Do's and don't of retrospectives.
4. How to effective track retrospective action items?
5. How JIRA can be used for tracking retrospective action items?
2. Mezocliq Proprietary and Confidential
2
About Mezocliq
meZocliq is a cloud computing company that provides an
innovative technology platform to facilitate big-data analytics
and business process transformation.
meZocliq offers an integrated application suite with end-to-
end functionality. Our suite unifies legacy data and enables
broad-ranging analytics, all at a fraction of the cost of other
alternatives.
New York | Noida
3. Mezocliq Proprietary and Confidential
3
Quick poll…
How many of us are
conducting retrospective
meetings consistently?
How many of us are
100% convinced about
improvements/results?
8. Mezocliq Proprietary and Confidential
8
Leveraging JIRA for tracking action items
Status wise
summary of all
action items
Owner wise summary
of action items
List of all OPEN action
items and their owners
Status of all action
items in swim lanes
for better visibility
Adding
retrospective
action items
to sprint
backlog is
quite
effective.
9. Mezocliq Proprietary and Confidential
9
How did it help us?
100% participation of team & not just attendance
50% reduction of recurring issues
20% improvement in sprints’ velocity
80% stories meeting DONENESS criteria (from 50%)
25% reduction in sprint spill overs
