Repository navigation
Scrum Documentation
Period: 27.10.23 - 9.11.23 Velocity: 13 Estimated time: 8w 3d 2h Time spent: 9w 3d 20m Underestimation of time: 4d 6h 20m Reports: Time Burndown chart

Estimated time: 1w 2d 2h Time spent: 1w 3d 7h 30m Story points: 13 Link: Technische Spielbasis
Tasks:
- Godot Tutorial
- We researched on the internet about Godot and watched tutorial videos on YouTube.
- In Godot eine Anwendung erstellen
- The goal was to install Godot and run an application on a mobile phone.
- The difficulty lay in connecting Godot with xCode to make it runnable on the iPhone.
- Github branches research
- Conduct a thorough examination of the existing branches in the GitHub repository, including their names, purposes, and any associated issues or pull requests.
- Designate specific GitHub users as required reviewers for the feature branch, ensuring that their approval is necessary for the merge to proceed.
- Simulate the merging process into the feature branch and verify that the system enforces the approval requirement, preventing merges without the necessary approval.
- GitHub/GitKraken anlegen
- Initially, we had to decide whether to use GitHub or GitKraken.
- The challenge at this point was that Godot could not connect directly to GitHub. Therefore, we decided to use GitKraken.
- Godot Anwendung auf einem Android Emulator
- Here, we took care of getting the application to run on an Android emulator.
- Now, an .apk file was automatically generated.
Estimated time: 2d Time spent: 1d 6h Story points: 1 Link: Anzeige von Ressourcen
Tasks:
- Darstellung von Ressourcen
- In this task, we focused on designing a suitable display for the resources (Mooneten and Moonstones).
- Due to discrepancies in the representation of resources, the display underwent multiple revisions and adjustments.
- The total time required for this task was only 7 hours, despite an estimated duration of 10 hours.
The user story was not completed in Sprint 1 because we did not have suitable textures for the resources.
Estimated time: 2d 2h Time spent: 2d 6h 30m Story points: 5 Link: Spielfläche mit begehbaren und nicht begehbaren Feldern
Tasks:
- Vordefinierter Bereich in dem der User sich bewegen kann
- A fixed area was set up where the user can move freely.
- The implementation of this task took 3 hours more than initially estimated due to discrepancies in the predefined area.
- Spielfeld Abgrenzung
- The entire playing field was enclosed to prevent the player from moving outside of it.
The user story was not completed in Sprint 1 because we did not find a suitable texture for the world.
Estimated time: 2d 2h Time spent: 2d 6h 30m Story points: 13 Link: Erstes Erscheinen des Charakters
Tasks:
- Textur Charakter
- We searched for a suitable texture for the character and ultimately decided to commission one, as we couldn't find a texture that met our requirements.
- The character was intended to be an astronaut in pixel art design.
- Einfügen des Charakters in Godot
- The character was inserted into the game with all animations, including idle and run animations.
- Bewegen des Charakters in Godot
- The character moves to the respective position by touching the screen.
- We had to acquire new skills for the implementation of this task, which is why the actual time spent (23h) was significantly higher than the estimated time of 8h.
- To allow the player to move not only in a straight line or directly to the position, we planned to implement a path-finding function for the next sprint.
Period: 10.11.23 - 23.11.23 Velocity: 26 Estimated time: 9w 3d 4h Time spent: 10w 1d 3h 50m Underestimation of time: 2d 7h 50m Reports: Time Burndown chart

Estimated time: 3d Time spent: 1d 7h Story points: 13 Link: Pipelines
Tasks:
- Adjust IOS Export
- Revise the iOS export process to ensure the correct export of the project for iOS devices and incorporate these adjustments into the pipeline.
- Pipelines anlegen
- Create the necessary pipelines for both Android and iOS to establish automated export processes, ensuring the project is exported correctly without manual intervention.
Estimated time: 1d Time spent: 7h Story points: 5 Link: Feldgrenze Erweiterung
Tasks:
- Kamera auf Player
- Fixing the camera on the player allowed for an expansion of the playing area.
- The player is now always positioned in the center of the screen.
- Additionally, the resource bar has been fixed to the upper-left corner of the screen.
-
Karte vergrößern- The map had to be enlarged to allow the player to move in a larger area.
- The issue here was that we lacked a suitable texture for the world, which is why the task couldn't be completed in this sprint.
-
Weltgrenze setzen- The world boundary could not be set yet because the map had not been enlarged.
- Therefore, this task had to be postponed to the next sprint.
Estimated time: 1d 1h Time spent: 1d 2h 30m Story points: 13 Link: Hauptgebäude
Tasks:
-
Collision erstellen- It was planned to set up collision for the main building to prevent the player from walking into the main building.
- Due to a missing texture, this task was not completed in Sprint 2.
-
Interaktion mit dem Hauptgebäude- Clicking on the main building opens a window.
- This was implemented by placing an invisible button on the main building.
- However, this task could not be completed due to the missing texture.
Estimated time: 1d 6h Time spent: 2d 4h Story points: 13 Link: Raumschiff Minispiel Steuerung
Tasks:
- Raumschiff-Steuerungssystem erstellen
- Controls were implemented for the spaceship in the first mini-game, allowing it to rotate in all directions and accelerate or decelerate.
-
Weltall-Feeling vermitteln- The player gets the sensation of being in space due to an implemented weightlessness effect.
-
Warp Around World- It was ensured that the mini-game has no field boundaries.
- Once the player's spaceship flies out of the playing field, it lands on the opposite side (Warp around world).
-
Geschwindigkeitskontrolle- Speed control was implemented to ensure that the player can only accelerate up to a certain speed.
- The player cannot exceed this speed.
Estimated time: 3d 7h Time spent: 3d 4h Story points: 13 Link: Raumschiff Minispiel Ablauf
Tasks:
- Zerfall von getroffenen Kometen
- The decay of impacted comets refers to their gradual disintegration or fragmentation over time following a collision.
-
Punkteberechnung- A point system has been implemented that increments the score upon a comet hit.
-
Kometen-Generierung- The comets have been introduced into the playing field in such a way that they appear at random positions on the field. New comets appear at predefined intervals.
-
Kollisionserkennung- The implemented collision detection responds to collisions between the spaceship and the comets.
-
Lebensverlust bei Kometen-Kollision- Upon collision between the player's spaceship and a comet, one life is deducted from the player.
Estimated time: 1d 6h Time spent: 2d 2h 30m Story points: 8 Link: Raumschiff Minispiel Setup
Tasks:
-
Lebensanzeige implementieren- The life indicator was implemented in the upper-left corner of the window, indicating to the player how many remaining lives they have before the game is over.
-
Kollisionsabfrage mit Kometen- The controls were revamped, and a joystick was added to facilitate simplified control of the spaceship.
-
GameOver-Funktionalität- The GameOver screen is displayed when the player has no lives left. An implemented life count monitoring ensures that the GameOver screen is shown at the appropriate moment.
-
Zurück zum Gebäude Button- A button was added to the mini-game, allowing players to return to the main game.
- Upon pressing the button, existing points are also credited as Mooneten.
-
Erneut spielen Button- A "Play Again" button was added, allowing the player to start a new game from the Game Over screen.
- This resets the player's points and lives.
Estimated time: 4d 2h Time spent: 1w 1d 1h Story points: 13 Link: Erstes Erscheinen des Charakters
Tasks:
- Path Finding für Charakter
- By clicking on the screen, the player walks to the selected position, navigating around obstacles.
- With a defined navigation region, the player can now find the shortest path to a selected position.
- Due to the complexity of the task, implementation took 1 hour longer than estimated.
Estimated time: 2d Time spent: 1d 6h Story points: 1 Link: Anzeige von Ressourcen
Tasks:
-
Balken anpassen- The number of resources should be represented as a ProgressBar.
- It was important to incorporate the ProgressBar into a fitting design.
- Due to time constraints, the completion of the bars was postponed to the next sprint.
-
Geeignete Textur für Mooneten und Moonstones finden- The two currencies were intended to be represented in the resource bar using appropriate textures.
- As we couldn't find suitable textures for the two resources in this sprint either, we decided to commission the textures in the next sprint to have them custom-made for us.
Estimated time: 2d 2h Time spent: 2d 6h 30m Story points: 5 Link: Spielfläche mit begehbaren und nicht-begehbaren Feldern
Tasks:
-
Textur für die Welt finden- We searched for a suitable texture for the world, but couldn't find one that met our requirements. For this reason, we decided to commission the world texture in the next sprint to have it custom-made for us.
Period: 24.11.23 - 7.12.23 Velocity: 61 Estimated time: 8w 3d 7h Time spent: 9w 6h 20m Underestimation of time: 1d 7h 20m Reports: Time Burndown chart

Estimated time: 1d Time spent: 7h Story points: 5 Link: Feldgrenze Erweiterung
Tasks:
- Karte vergrößern
- With a suitable texture now available for the world, the playing field could be expanded.
- The map was designed large enough to accommodate all planned building areas on the playing field.
- Weltgrenze setzen
- In line with the expanded map, the world boundary was redefined based on set collisions to demarcate the new playing field.
- The boundary was set to be visually apparent for the player.
Estimated time: 1d 1h Time spent: 1d 2h 30m Story points: 13 Link: Hauptgebäude
Tasks:
- Collision erstellen
- Collisions were created for the main building to prevent the player from walking into it.
- Interaktion mit dem Hauptgebäude
- With the missing texture now available, the interaction with the main building could be completed.
Estimated time: 3h Time spent: 1h 30m Story points: 1 Link: Hauptgebäude Textur
Tasks:
- Textur für Hauptgebäude
- A suitable texture for the main building was selected. It is a 2D pixel art rocket.
Estimated time: 1d 6h Time spent: 2d 4h Story points: 13 Link: Raumschiff Minispiel Steuerung
Tasks:
- Weltall-Feeling vermitteln
- The player gets the sensation of being in space due to an implemented weightlessness effect.
- Warp Around World
- It was ensured that the mini-game has no field boundaries.
- Once the player's spaceship flies out of the playing field, it lands on the opposite side (Warp around world).
- Geschwindigkeitskontrolle
- Speed control was implemented to ensure that the player can only accelerate up to a certain speed.
- The player cannot exceed this speed.
Estimated time: 3d 7h Time spent: 3d 4h Story points: 13 Link: Raumschiff Minispiel Ablauf
Tasks:
- Kollisionserkennung
- The implemented collision detection responds to collisions between the spaceship and the comets.
- Lebensverlust bei Kometen-Kollision
- Upon collision between the player's spaceship and a comet, one life is deducted from the player.
Estimated time: 1d 6h Time spent: 2d 2h 30m Story points: 8 Link: Raumschiff Minispiel Setup
Tasks:
- Lebensanzeige implementieren
- The life indicator was implemented in the upper-left corner of the window, indicating to the player how many remaining lives they have before the game is over.
- Kollisionsabfrage mit Kometen
- The controls were revamped, and a joystick was added to facilitate simplified control of the spaceship.
- GameOver-Funktionalität
- The GameOver screen is displayed when the player has no lives left. An implemented life count monitoring ensures that the GameOver screen is shown at the appropriate moment.
- Zurück zum Gebäude Button
- A button was added to the mini-game, allowing players to return to the main game.
- Upon pressing the button, existing points are also credited as Mooneten.
- Erneut spielen Button
- A "Play Again" button was added, allowing the player to start a new game from the Game Over screen.
- This resets the player's points and lives.
Estimated time: 2d Time spent: 1d 6h Story points: 1 Link: Anzeige von Ressourcen
Tasks:
- Balken anpassen
- The ProgressBar for the resource display was completed. The Mooneten and Moonstone are now represented in the ResourceBar.
Estimated time: 2d 2h Time spent: 2d 6h 30m Story points: 5 Link: Spielfläche mit begehbaren und nicht-begehbaren Feldern
Tasks:
- Textur für die Welt finden
- A suitable texture for the world was found.
- The principle is based on a TileMap.
- This allowed us to design the world as we deemed appropriate.
- The world has a texture resembling a lunar surface. Additionally, there are craters on the world representing building areas.
- Furthermore, there is a path leading to the planned shop.
- Klicken auf nicht begehbare Felder
- When a player clicks on a non-traversable field (building field), they move to the field and stop in front of it.
- Flackern bei Kollision mit nicht-begehbarem Feld
- The issue was resolved, although it posed a significant challenge as the player's collisions had to be reworked. This required extensive trial and error until the problem was fixed.
Estimated time: 1d 2h Time spent: 1d 1h Story points: 8 Link: Ressourcen Logik
Tasks:
- Functions for addition, subtraction, get and set
- Getter and setter procedures were implemented for each resource (Mooneten and Moonstone).
- Additionally, addition and subtraction procedures were implemented for each resource to manage the resources accordingly.
- Save resource data in file
- A file was created to allow the current amount of Mooneten and Moonstone to be saved.
- Every time the amount of Mooneten or Moonstone is changed, that respective quantity is saved in the file, ensuring persistence.
- Save Unix-Timestamp on exit
- Once the player closes the game, this moment is recorded in the file.
- The challenge was figuring out whether the application on the phone is closed when pressing the Back button on Android, or if the app is simply left running in the background without closing it.
- Read resource data file
- Upon starting the game, the resources (Mooneten and Moonstone) and the Unix timestamp are loaded from the file.
Estimated time: 1d Time spent: 1d Story points: 8 Link: Ressourcenproduktion Logik
Tasks:
- Nach erneutem Start Ressourcen hinzufügen
- Upon starting the game, the timestamp representing the last time the game was closed is converted to minutes and multiplied by a factor of 10 since the player can earn a maximum of 10 Mooneten per minute.
- A limit of 1000 Mooneten was set, meaning the player cannot earn more than 1000 Mooneten while the game is closed.
- Timer einbauen während Laufzeit
- A timer was implemented, renewing itself every minute.
- This timer, upon timeout, invokes a procedure that credits the player with 10 Mooneten.
Period: 8.12.23 - 21.12.23 Velocity: 68 Estimated time: 9w 1d 2h 30m Time spent: 9w 2d 4h 15m Underestimation of time: 1d 1h 45m Reports: Time Burndown chart

Estimated time: 3d 7h Time spent: 3d 4h Story points: 13 Link: Raumschiff Minispiel Ablauf
Tasks:
- Punkteberechnung
- A point system has been implemented that increments the score upon a comet hit.
- Kometen-Generierung
- The comets have been introduced into the playing field in such a way that they appear at random positions on the field. New comets appear at predefined intervals.
Estimated time: 2d Time spent: 1d 6h Story points: 1 Link: Anzeige von Ressourcen
Tasks:
- Geeignete Textur für Mooneten und Moonstones in Auftrag geben
- We commissioned suitable textures for the two resources. A yellow 'M' was chosen for the Moonetes, and a diamond-like texture for the Moonstones.
Estimated time: 4h Time spent: 3h 30m Story points: 5 Link: Pipelines Storage Bug
Tasks:
- Delete artifacts manually
- Manually delete unnecessary artifacts to free up storage space and resolve the current storage issue.
- Research
- Investigate the root cause of the artifacts storage full issue to implement a more permanent and preventive solution.
- Pipeline import new action
- Integrate a new pipeline action to import artifacts more efficiently, optimizing storage usage and preventing unnecessary accumulation.
- Delete build artifacts
- Implement a task to automatically or systematically delete build artifacts after a certain period or when they are no longer needed, ensuring ongoing storage optimization.
Estimated time: 3d Time spent: 3d 2h 40m Story points: 13 Link: Minispiel 2 Logik
Tasks:
- Charaktersteuerung
- The character can move by pressing on the screen, having the option to switch between 4 fixed lanes.
- Charakterspeed
- The character moves continuously forward.
- Additionally, the character speeds up over time to increase the difficulty of the game.
- Objekt spawner
- Comets appear randomly on one of the 4 lanes at the top of the screen.
Estimated time: 4h Time spent: 1h 30m Story points: 2 Link: Minispiel 2 Aussehen
Tasks:
- Hintergrund auswählen
- The background of the mini-game represents outer space. It consists of a dark background with small colorful stars.
- The objects moving toward the player are comets.
- Figur auswählen
- The rocket from the main game was used as a suitable texture for the player.
Estimated time: 4h Time spent: 4h Story points: 8 Link: Minispiel 2 Pause-Menü
Tasks:
- Pause-Menü
- A pause menu was implemented. An icon appears in the upper right corner of the screen, allowing the player to pause the mini-game through interaction.
- The player now has the option to resume the game or exit the mini-game and return to the main game.
- If the player chooses to resume the game, a countdown is initiated, counting down from 3 before the mini-game is definitively resumed.
Estimated time: 6h Time spent: 5h 45m Story points: 5 Link: Minispiel 2 Gameover-Screen
Tasks:
- Retry-Button
- Once the player has lost, they have the option to play another round through the Retry button.
- This resets the score and speed.
- Score und Highscore Logik
- In the Game Over screen, the current score and the high score are displayed.
- If the score is greater than the high score, the new high score is set and displayed.
- Exit-Button
- The player has the option to exit the mini-game and return to the main game through an Exit button.
Estimated time: 4d Time spent: 4d 5h Story points: 13 Link: Inventar Logik
Tasks:
- Menü öffnen mit 4 verschiedenen Gebäuden zur Auswahl
- A window was implemented, displaying 4 different buildings for selection (Mooneten Generator, Moonstone Generator, Mooneten Storage, Moonstone Storage).
- Interaktion mit Feld möglich
- The 14 craters scattered on the map can now be clicked.
- Each field has been assigned a unique ID for identification purposes.
- Auswahl von Gebäuden
- The buildings in the inventory can be selected and logically placed on the field. This reduces the quantity of that building type by one.
- Anzeige von Anzahl der verfügbaren Gebäude
- For each building type, a quantity of that particular building was implemented. It indicates how many buildings of each type the player owns and can place.
- Unterscheidung der Gebäude möglich
- Each building type has been assigned a fixed ID, providing the ability to distinguish which building type is on the field.
Estimated time: 2d 1h 30m Time spent: 2d 4h 10m Story points: 8 Link: Optionbar für Hauptgebäude
Tasks:
- Setup overview
- Configure the initial setup of the option bar to ensure a cohesive and functional interface.
- Resource field (view)
- Design and implement the resource field area to display the current capacities of Mooneten and Moonstones.
- Show picture of building
- Implement the display of the building's image within the option bar for visual identification.
- Play button
- Integrate a "Play" button within the option bar to initiate the associated minigame upon user interaction.
- Show the name and level of building (view)
- Display the name and current level of the building at the top of the option bar.
- Close button
- Implement a "Close" button at the top right of the option bar to enable users to close the window.
Estimated time: 1d 4h Time spent: 1d 4h 20m Story points: 4 Link: StartMenu
Tasks:
- Oberflächen Design
- A start menu has been designed. In the upper left corner is the title of the game "MESSAG".
- The background chosen is a lunar surface with a rover in the center.
- There are also 3 buttons on the right side (Continue, New Game, and Legal Notice).
- Impressum Szene designen
- The Legal Notice scene displays the title of the game, as well as the names of the 5 developers of the game.
- Logik von StartMenü
- Pressing the Continue button continues the game from the current state.
- If the player presses the New Game button, a new game state is created, and the game starts.
- The Legal Notice button switches to the Impressum scene.
Period: 22.12.23 - 18.01.24 Velocity: 108 Estimated time: 10w 3d 6h 30m Time spent: 11w 2d 3h 25m Underestimation of time: 4d 2h 10m Reports: Time Burndown chart

Estimated time: 7h Time spent: 5h 10m Story points: 2 Link: Shop Interface
Tasks:
- Close button
- Integrate a close button within the shop interface to provide users with a convenient and intuitive option to exit the shopping view, thereby enhancing overall user experience and navigation.
- Resource display
- Implement a resource display feature in the shop interface to provide users with real-time visibility into available resources, facilitating informed decision-making during the shopping process.
- Setup interface
- Design and implement a setup interface for the shop.
- Shop label
- Introduce a prominent and descriptive label within the shop interface to clearly communicate the purpose and content of the displayed items, ensuring a more user-friendly and informative shopping environment.
Estimated time: 1d Time spent: 2h 20m Story points: 8 Link: Shop - Building Cards
Tasks:
- Setup interface
- Create a setup interface for building cards within the shop.
- Building Name label
- Incorporate a clear and descriptive label for building names within the shop interface to enhance user understanding and streamline the selection process when browsing through available structures.
- Building Image
- Include visual representations of buildings by adding building images in the shop interface, providing users with a more intuitive and visually informative experience when selecting structures.
- Buy Button
- Integrate a conspicuous "Buy" button in the shop interface, facilitating a straightforward and user-friendly process for customers to purchase selected items or services.
Estimated time: 1d 4h Time spent: 1d 4h 20m Story points: 4 Link: StartMenu
Tasks:
- Confirm on new game
- Implement a confirmation prompt within the Start Menu to confirm user intent when clicking on "New Game," enhancing user experience by preventing accidental initiation of a new game session.
Estimated time: 2d 5h Time spent: 2d 2h Story points: 13 Link: Display of Buildings
Tasks:
- Display of buildings logic
- Implement the "Display of Buildings" logic to enable players to click on available buildings in their inventory, automatically placing the selected building on a predefined, non-walkable circle, and ensuring it is visually displayed for the player's interaction and observation.
- Create building scenes and place them in the world
- Develop building scenes and integrate them into the game world, ensuring seamless placement within the environment for players to interact with and enhance the overall gaming experience.
Estimated time: 1d 4h Time spent: 1d 3h 40m Story points: 13 Link: Upgrade buildings
Tasks:
- Hauptgebäude cancel-Button Textur finden und implementieren
- Find and implement the texture for the cancel button in the main building upgrade interface.
- Add Upgrade Storage Size
- Implement an upgrade mechanism that increments the storage size of the building upon upgrading, enhancing the overall capacity and functionality of the upgraded structure.
- Upgrade main building
- Upgrade the main building (rocket) to increase its capacity for both mooneten and moonstones, providing players with expanded storage capabilities and enhancing resource management in the game.
- Check needed Resource for upgrade
- Implement a system to check and display the required resources for upgrading the main building (rocket), providing players with clear information on the necessary resources before proceeding with the upgrade.
Estimated time: 1d Time spent: 1d 2h Story points: 5 Link: Map
Tasks:
- Texture minimap button
- Design and implement the texture for the minimap button, ensuring a visually appealing and intuitive icon for users to access the minimap feature.
- Minimap
- Implement the minimap logic to accurately display the game environment and player position, focusing on essential elements for navigation without cluttering the view with unnecessary points of interest.
- Show Resourcebar bug
- Resolve the bug where the resource bar remains visible when clicking on the minimap, ensuring that the resource bar behaves appropriately and does not persist when interacting with the minimap.
Estimated time: 1d Time spent: 1d 7h Story points: 5 Link: Integrate Optionmenu for New Buildings
Tasks:
- Create a dynamic optionbar for all buildings
- Create a dynamic option bar that accommodates all buildings.
- Connect the buildings with their optionbars via code
- Establish a code-based connection between the buildings and their respective option bars to enable seamless integration and interaction within the game interface.
Estimated time: 2d 1h Time spent: 2d Story points: 13 Link: Automatic Resource Storage in Generators with Capacity Limit
Tasks:
- Display resource production in building
- Develop a feature to visibly showcase the ongoing resource production within the generator building, providing players with information on the generated resources.
- Production during runtime
- Implement a mechanism to ensure that resource production occurs dynamically during gameplay, reflecting the progression of in-game activities.
- Capacity limit
- Integrate a capacity limit for automatic resource storage within generators, preventing any potential overflow and establishing a structured resource management system for a more immersive and balanced gaming experience.
- Offline production with limit
- Implement an offline production feature for generators with a maximum capacity limit of 1000, allowing players to accumulate resources during periods of inactivity up to the specified limit.
Estimated time: 1d 2h Time spent: 1d 6h 30m Story points: 13 Link: Shop Logic
Tasks:
- Shop logic
- Implement shop logic to move purchased buildings to the user's inventory, deactivate and gray-out the "Buy" button when resources are insufficient, perform resource checks, visually indicate unavailability after a failed purchase, and display available resources.
Estimated time: 1d 3h 30m Time spent: 2d 30m Story points: 13 Link: Inventory
Tasks:
- Logic
- Develop the backend logic for the inventory system, incorporating functionality that allows for efficient storage and retrieval of building data, ensuring a seamless and responsive user experience.
- Design
- Create a visually appealing and user-friendly inventory interface, drawing inspiration from the shop's design to maintain consistency across the user interface, fostering a cohesive and intuitive gameplay environment.
- Take buildings back into inventory
- Implement the necessary code to enable users to take buildings back into their inventory, establishing a dynamic system that supports the fluid movement of structures between the inventory and the game field.
- Texture for remove button in optionbar
- Design an aesthetically pleasing texture for the remove button within the inventory's option bar, ensuring it aligns with the overall visual theme, providing users with a clear and engaging element for interacting with the inventory items.
Estimated time: 1w Time spent: 4d 2h 45m Story points: 13 Link: Documentation
Tasks:
- Technical documentation
- Create comprehensive technical documentation that includes information on the technologies, programming languages, frameworks/libraries, data storage, and any other technical aspects crucial to the app's development and maintenance.
- Contribution guide
- Develop a contribution guide that outlines startup instructions, pull request requirements, branch explanations, details on versions and release management, and information about any code analysis tools or CI pipelines utilized in the project.
- User documentation
- Generate user documentation with a step-by-step guide, ensuring clear and understandable instructions for each feature from the user's perspective, enhancing the overall user experience and understanding of the application.
- Code documentation
- Implement thorough code documentation to provide insights into the codebase, including comments, inline documentation, and any necessary explanations that enhance code readability and maintainability.
- Scrum documentation
- Establish Scrum documentation that includes traceability, detailed implementation descriptions, and records of technical issues encountered during the implementation of user stories/tasks, ensuring a transparent and well-documented development process.
Estimated time: 6h Time spent: 6h Story points: 1 Link: Optimize Spaceship Controls for Enhanced Player Experience
Tasks:
- Customize graphics
- Enhance the visual elements associated with the spaceship controls in the first mini-game to align with the overall design aesthetics and create a more engaging and immersive gaming environment.
- Optimize Spaceship Controls for the first Mini-Game
- Modify the existing spaceship controls to incorporate an enhanced joystick mechanism, focusing on improving responsiveness and precision for smoother navigation during the first mini-game.
Estimated time: 1d 4h Time spent: 1d 6h Story points: 8 Link: Resource and Generator Management
Tasks:
- Distribute Resources Across Storage Buildings
- Develop a mechanism that automatically distributes Mooneten and Moonstones across all connected storage buildings, ensuring an even spread of resources. When one storage building reaches its capacity, the system should intelligently redirect resources to the next available building.
- Collect resources from generators
- Implement functionality allowing users to collect resources generated by specific generators, ensuring a seamless process that contributes to resource accumulation and utilization.
- Max resources should depend on storage building capacity
- Implement logic that dynamically adjusts the maximum allowable resources based on the capacity of the associated storage buildings, preventing resource overflow and maintaining a realistic and balanced resource management system.
Estimated time: 5h Time spent: 6h 30m Story points: 3 Link: Update Graphics
Tasks:
- Can't open some Scenes
- Address and resolve the bug that prevents the opening of certain scenes, ensuring smooth navigation and gameplay without any hindrances.
- Connect new Images
- Integrate updated graphics for buildings and resources, replacing placeholder visuals to provide users with a more visually appealing and immersive gaming environment.
Estimated time: 3d 1h Time spent: 4d 7h 20m Story points: 5 Link: Project Cleanup
Tasks:
- Code clean up
- Conduct a comprehensive clean-up of the codebase to remove redundancies, improve code organization, and enhance overall maintainability.
- General BugFixes
- Identify and rectify any general bugs present in the application, ensuring a smoother and more reliable user experience.
- Player Movement Bug
- Specifically address and resolve any issues related to player movement, ensuring fluid and responsive control within the game.
- GeneralFixes
- Implement fixes for miscellaneous issues that may impact the application's performance or user interaction.
- Minigame Code Cleanup
- Perform a targeted clean-up of code related to the minigames, focusing on improving code structure and eliminating potential sources of bugs.
Estimated time: 1d Time spent: 1d 2h Story points: 2 Link: Quality Check - PipeLine
Tasks:
- GDLint + GDFormat
- Implement GDLint and GDFormat tools to perform static analysis and formatting on the codebase, enforcing consistent coding standards and improving overall code quality.
- Testing Sonarcloud
- Integrate Sonarcloud testing to conduct static code analysis, identify code smells, bugs, and security vulnerabilities, and ensure compliance with best coding practices.
- Python Script for DataType
- Develop a Python script for data type validation, enhancing data integrity and preventing potential runtime errors through comprehensive checking of data types within the codebase.
Period: 27.10.23 - 18.01.24 Reports: Time Burndown chart Working hours Time estimation
