Sprint 3 - SwEng-UCM/P_Tactics GitHub Wiki

Documentation describing the sprint 3, done and developed between the 26/02/2025 - 18/03/2025.
Included in the documentation the Sprint Planning, the Sprint Review and the Sprint Retrospective

Sprint Planning

The sprint goal for this sprint is: "Give diversity and dynamism to the game, with new maps, mechanics and type of troops." We are focusing on the development of characteristic features of our game, such as a sniper, a melee attacker and an attack soldier, amongst others. We have selected the following user stories to be implemented into the game:

1. Story 7 - TROOPS:

Description: "As a user I want to be able to have a sniper troop with a special ability, range and movement so the game has more variety."
Size: Medium (Around 3-4 hours).
Priority: P1 (Important for the development).

2. Story 8 - TROOPS:

Description: "As a user I want to be able to have a melee troop (nickname "Cloaker") with a special ability, range and movement so the game has more variety."
Size: Medium (Around 3-4 hours).
Priority: P1 (Important for the development).

3. Story 9 - TROOPS:

Description: "As a user I want to be able to have a attack soldier (nickname "FastSoldier") with a special ability, range and movement so the game has more variety."
Size: Medium (Around 3-4 hours).
Priority: P1 (Important for the development).

4. Story 10 - TROOPS:

Description: "As a user I want to be able to have a smoker troop with a special ability, range and movement so the game has more variety."
Size: Medium (Around 3-4 hours).
Priority: P1 (Important for the development).

5. Story 8 - BOARD:

Description: "As a user I want to be able to have a variety of maps to choose from when playing, so the game is more interesting."
Size: Medium (Around 3-4 hours).
Priority: P2 (Needed for the development).

Sprint Review

We achieved the sprint goal, created the new mechanics and troops, and there is also a map selector to choose maps easily into the game.

• Created new troops (now we have a sniper, a smoker and a lightTroop).
• Map Selector and maps can be added and chosen easily.
• The code has been cleaned and refactored.
• We have selected our Team Advocate and Documentation lead to be Alyssa Chioldin.
• Redid the product backlog, added a few more user stories and resized them with planning poker.

We may add new troops and mechanics in the following sprints, and improve the map selector after the development of GUI.

Sprint Retrospective

What went well during the sprint?

The use of smaller and more compact user stories, the improvement of the product backlog and the division into smaller pieces with shorter deadlines improved the efficiency and work capacity of the project, and enabled us to dedicate a few days to debug and find errors properly.

What went wrong during the sprint?

Whilst the sprint went well, the code developed is unclear and without comments, making the logic of the game less intuitive and harder to understand for other members and foreigners. Furthermore, the differences between our ideas sometimes are left not specified, creating a difference of concepts between the members.

What can we learn and improve for the next sprint?

Explaining the developed code, either by comments and/or meetings, will improve the cohesion of the team. We will also improve the internal debates to be settled faster and clearer.