In a high-velocity sprint, developers need to cut corners, make some compromises, and push fun tasks to the next sprint. Retrospective meetings are future judgment-free zones, where developers can put today’s frustrations.
Two questions drive retrospectives: “What went well?” and “What needs improvement?“
The funny thing about these meetings is that people see processes and structure as something that went well, as well as potential improvements.
A well-documented user stories, other developers following the git-flow to the letter, and updated JIRA boards are usually cherished. Not having detailed product requirements, developers shipping features too soon to QA, of leaving the sandbox server a mess, are common complaints.
In most of the retrospective meetings, you will be dancing between agility and formality.
- Human-in-the-Loop for Bias Mitigation - 10/16/24
- Challenges in Implementing Federated Learning in Ad Tech - 10/09/24
- Graph Neural Networks for RTB Systems - 10/02/24