Sprint 4 - SwEng-UCM/P_Tactics GitHub Wiki
Documentation describing the sprint 4, done and developed between the 18/03/2025 - 08/04/2025. Included in the documentation the Sprint Planning, the Sprint Review and the Sprint Retrospective
Sprint Planning
Sprint Goal: For the fourth sprint, we are going to develop a functional display of the game outside the console with all the details possible (visibility, walls, traps ...), creating a more intuitive and formal graphical interface. In other words, the GUI.
In addition, we are aiming to develop a flexible and maintainable system for adding components in future sprints.
For sprint 4 we chose the following user stories to implement:
(With same enumeration and category as in Product Backlog)
(All tasks are considered small since the WindowBuilder plugin has eased the workload immensely)
1. Story 1 - GUI:
Description: "As a user I want to be able to see the map, so I can see and intuitively understand what is happening in the game."
Size: Small (Less than 2 hours).
Priority: P0 (Vital for the development).
2. Story 2 - GUI:
Description: "As a user I want to be able to execute the commands over the GUI, so it is easier to execute the commands."
Size: Medium(Around 2-3 hours).
Priority: P0 (Vital for the development).
3. Story 3 - GUI:
Description: "As a user I want to be able to click on my troop to select it, so it is easier to move and do my turn."
Size: Small (Less than 2 hours).
Priority: P0 (Vital for the development).
4. Story 4 - GUI:
Description: "As a user I want to be able to get help / instructions, to understand how to play the game."
Size: Small (Less than 2 hours).
Priority: P0 (Vital for the development).
5. Story 5 - GUI:
Description: "As a user I want to be able to (once I select a troop) move my troop by clicking in the cell to move."
Size: Small (Around 2-3 hours).
Priority: P0 (Vital for the development).
6. Story 6 - GUI:
Description: "As a user I want to have a main window so the game looks more professional and well built."
Size: Small (Less than 2 hours).
Priority: P2 (Needed but not crucial for the development).
7. Story 2 - Requirements:
Description: "As a user I want to be able to have an undo command, so I can undo my actions in case I have made an error."
Size: Medium (Around 2-3 hours).
Priority: P1 (Important for the development).
Sprint Review
We achieved the sprint goal, created a successful and good-looking graphical interface for the user, which is intuitive and makes this game more easy to understand for the new players. However, as a team, we dedicated more time than we estimated in the development of the GUI and underestimated a user story, so we could not complete all user stories.
- "As a user I want to be able to have an undo command, so I can undo my actions in case I have made an error." NOT COMPLETED.
On the brightsight, we have a sketch of how to implement it in our program.
Sprint Retrospective
What went well during the sprint?
The use of plugins and different resources we knew/learnt were an incredible help to the development. Good communication and the daily reunions have been a good help to find and correct the issues and bugs in our project.
What went wrong during the sprint?
We faced several problems during this sprint, the late start of the sprint, certain problems with the plugins in some members and the development of a closed part of the game (the GUI) caused a bottleneck, where the work was not distributed properly and where certain members have not been able to contribute as much as others.
What can we learn and improve for the next sprint?
We have taken notes of the mistakes and misunderstandings that happened during the sprint, and determine to (for future sprints) establish clearer and specially close objectives to all members (as sometimes we complete other tasks apart from the one we were assigned), doing the meetings earlier to assure enough time to work and debate less on how to solve certain problems.