DeveloperWeek 2023

Ketaki Vaidya, Product Manager-AI,  Oracle

Description
The majority of modern software development teams adhere to the Agile methodology to encourage continuous testing and development over the course of their product lifecycle. After every iteration, these teams usually conduct a Retrospective meeting.
The goal of this meeting is simple: reflect on the previous work increment and come up with a plan to improve the next one. Only a few teams, though, have mastered the art of running productive retrospectives. In this session, we'll examine the best practices for running retrospectives the right way.

Takeaways
1. Why should you have a Retrospective meeting?
2. How to draft a working agreement for your team?
3. Gathering Relevant Data before the meeting.
4. Key questions that can drive your retrospective discussion?
5. Connecting the dots: Use the takeaways from the last retrospective to guide the next one.
6. Having a retrospective meeting is not enough. Complement it with a follow-up action strategy.
7. (Bonus tip) Make it personal: Extend the retrospective practice to track your personal goals.