Sprint 1 - SwEng-UCM/P_Tactics GitHub Wiki

Documentation describing the sprint 1, done and developed between the 04/02/2025 - 09/02/2025. Included in the documentation the Sprint Planning, the Sprint Review and the Sprint Retrospective

Sprint Planning

For the first sprint, we wanted to establish the foundations of the project and make sure that all the developers have the same view of the project. So, we agreed to do:

  1. Creation of the repository, as well as the project to set our issues and plan the next sprints
  2. Development of the product backlog.
  3. Development of the Agile Inception document.
  4. Creation of UML diagrams and examples to make sure we were on the same page and avoid misunderstandings.

The sprint goal is to develop a functional display of the map and troops, with all the details possible (visibility, walls, traps ...) as well as develop a flexible and maintainable foundation for future sprints.
For sprint 1 we chose the following user stories to implement: (With same enumeration and category as in Product Backlog)

1. Story 1 - BOARD:

Description: "As a user I want to have a map / board with coordinates so I can see the different elements of the game."
Size: Medium (Around 2-3 hours).
Priority: P0 (Vital for the development).

2. Story 2 - BOARD:

Description: "As a user I want the map to include walls so it is not empty and boring."
Size: Medium (Around 2-3 hours).
Priority: P1 (Important for the development).

3. Story 3 - BOARD:

Description: "As a user I want the map to only show information my troops can see in order to make strategy more interesting."
Size: Large (Around 3-4 hours).
Priority: P0 (Vital for the development).

4. Story 1 - TROOPS:

Description: "As a user I want my troops to move so I can command them."
Size: Large (Around 3-4 hours).
Priority: P0 (Vital for the development).

5. Story 1 - DEVELOPER:

Description: "As a pair of users we want the game to change views from one another so we can play together."
Size: Large (Around 3-4 hours).
Priority: P1 (Important for the development).

6. Story 2 - DEVELOPER:

Description: "As a user I want to be able to get help/instructions, to understand how to play the game"
Size: Medium (Around 2-3 hours).
Priority: P1 (Important for the development).

Sprint Review

During the sprint we have achieved most of our objectives, and worked in different aspects:

  • We have determined the roles of the team as follows: Timofey Matveev, the GitHub Master; Arturo Hernández Escobar, the Product Owner; and Sergio Macías Valdés, the Scrum Master.
  • We have developed the user stories of the project, and included them in the product backlog.
  • We created the Agile inception document and the different issues inside the project.
  • We started developing the project according to the user stories.

Sprint Retrospective

What went well during the sprint?

The team showed great teamwork during the development of the backlog, where we all are understanding the project and being able to contribute and debate the ideas proposed. The work was also distributed equally and done properly, and the creation of different roles makes the team work in an organized way.

What went wrong during the sprint?

We had some issues developing the project and issues (the user stories) which delayed work and caused confusion in the team. We are also adapting to the Scrum method, and adapting to the daily meetings and the sprint planning. It is worth mentioning that we have certain problems debating and agreeing in certain parts of the game, causing a loss in time and productivity.

What can we learn and improve for the next sprint?

We mostly need to continue working and learning about the Scrum methodology, so we can be more efficient in the meetings and development of code, as well as being faster with the sprint planning and the division of work. We also need to learn more about Github and how to use it correctly. We will develop a system for faster debates and opinions.