04: Iteration Review - ZHAW-Team-Toxic/PM4-Team-Toxic GitHub Wiki

Iteration Goal:

Brief summary of what the iteration aimed to achieve.

1. Achievements

1.1 Completed Issues

1.2 Issue Carryover

#76
#121

2. What Went Well

Strong teamwork: Tasks were clearly assigned and dependencies were addressed early.
Expanded Issues: Newly created issues were formulated in greater detail ("mehr Fleisch auf den Knochen"), making them easier to implement.
Active support within the team: Team members readily offered help when technical problems arose.
Communication was efficient and reliable throughout the sprint.

3. Challenges & Lessons Learned

Challenges:

Managing dependencies between issues was sometimes difficult and led to minor delays.
Processing of pull requests (PRs) occasionally became a bottleneck, as not all team members regularly reviewed PRs.

Lessons Learned:

Clearer agreements on prioritizing and distributing PR reviews would help avoid bottlenecks.
Even though the self-organization worked well, explicit PR responsibilities could further improve efficiency.

4. Blockers / Open Issues

Work on the NoTech product (game booklet) was consciously postponed to the next iteration, as a minimum level of gameplay is necessary to meaningfully describe the game content.

6. Feedback & Suggestions

Improve the distribution and prioritization of PR reviews to avoid review backlogs.
Maintain the current strong communication culture, even as task complexity grows.

7. Retrospective Summary

Overall, the iteration went well.
The main features and tasks were completed successfully, and teamwork was strong.
Although some technical dependencies caused minor delays, most blockers were resolved independently or pragmatically moved to the next iteration.
Moving forward, we will focus on faster PR handling and aligning the development of the NoTech product with the gameplay progress.