Skip to content

Planning & Refinement 1‐3

Daan Kikkert edited this page Jun 11, 2024 · 4 revisions

Planning Sprint 1:


Sprint 1 staat in het thema van core gameplay. We willen graag een basis hebben voor de game om op verder te bouwen.

De volgende features zullen deze sprint gedeveloped worden:

  • Basic WASD player movement
  • Mouse to world postion turning
  • Health script adjustable for any object needing an health script
  • Enemies
  • Wave spawner
  • Basic attack system adjustable for anything which needs to attack

Planning Sprint 2:


Deze sprint wordt gebruikt voor het implementeren van de core pillars. Deze core pillars zijn naast de pure core gameplay de belangrijkste elementen van de game. We hebben voor elke core pillar een feature bedacht.

Always live:

  • Voor deze pillar zouden we graag networking willen toevoegen, maar onderzoek loopt niet soepel. Als alternatief hebben we het idee om fake AI players toe te voegen.

Cooperative gameplay:

  • Ons core game concept zorgt in theorie al voor cooperative gameplay.

Universal communication:

  • We hebben bedacht om Ping en Emotes toe te voegen voor communicatie. Emotes zijn de meer sociale/leuke communicatie, en pings meer tactisch/serieus.

Online persistence:

  • We wilden weapon unlocks hebben voor de speler doormiddel van het spelen van de game.

Instant gaming:

  • We zullen bij het maken van assets simpelweg moeten letten op performance.

Ook gaan we deze sprint de gameplay loop afronden en een aantal features aanscherpen.

De volgende features zullen deze sprint gedeveloped worden:

  • Class manager
  • Props
  • Shop
  • Game reset
  • Re made enemies
  • Animations
  • Enemy models imported
  • Castle model imported
  • Player model imported
  • Bug fixes
  • Emotes
  • Fake Player
  • Build for the game

Sprint refinement Sprint 2:

-US-01: As a player I want to be able to move so I can go to important locations
The player movement is fully functional and implemented in the development branch and is therefore complete

-US-02: As a player I want enemies that come for me so I have something that threatens me
The enemy script is functional and implemented in development and is therefore complete

US-03: As a player I want to play the game online so I can play with my friends and have more fun in the game.
The networking is being researched. We already expected this userstory to last more than one sprint as all of us had little experience with networking.

US-04: As a player I want to be able to attack so I can defeat the enemies.
The player has a simple attack system that is able to damage the enemies. This has been implemented into development and is therefore done.

US-05: As a player I want to be able to use different weapons with different ammunition types so I can have some gameplay variety.
The system itself is completed, however it still needs to be implemented into the develop branch and is therefore barely unfinished.

US-06: As a player I want a base to defend from enemies so that I can lose the game
The base uses the universal health script and can be destroyed which resets the game. However the reset script has not been implemented into develop and the feature is therefore not complete.

US-07: As a player I want the enemies to spawn in scaling waves so that the game gets more challenging
There is a system to spawn waves of enemies, however it doesn’t yet spawn waves when the previous wave is completed. Therefore the feature is not finished.

US-19: As a developer I want a generic health script which I can apply to any item so I can use it on anything which has health
The health script is done and has been implemented into development and the feature is complete.

Planning Sprint 3:


Sprint planning sprint 3

Dit sprint gaat vrijwel puur om het afronden, integraten en refinen van de features die al bestaan. We zullen niet starten met het maken van nieuwe features. Het snel hebben van een betere build en deze (user)testen gaat erg belangrijk zijn deze sprint. Vanuit deze tests moeten duidelijke test result logs gemaakt worden vanuit waar we nieuwe bugfix todo’s moeten gaan maken. We hebben besloten om networking te laten liggen en in plaats daarvan AI players toe te voegen. Omdat het onderzoek naar networking niet soepel verliep zouden we nu elk script om moeten bouwen naar een network object, en dat leek ons niet realistisch.

Features die nog afgerond moeten worden:

  • Ping system

Het ping system moet andere visuals krijgen per ping

  • Experience system

De player moet nog experience krijgen als enemies worden verslagen

  • AI players

De AI players moeten nog attacken

Features die nog geintegrate moeten worden:

  • Ping system
  • Emote system

Deze features zijn beide ready for integration.

Known bugs om te fixen:

  • Als de enemy/speler doodgaat tijdens een melee attack crasht de game
  • De enemy hit soms het kasteel niet

Punten voor optimalisatie:

  • Enemy targeting system moet geoptimaliseerd worden aangezien er veel spawnen.

Verdere potentielë bugfixes en optimalisatie zal moeten blijken uit testing.

Sprint refinement sprint 3:

- US-10: As a player I want to gain experience for my classes so that I have a sense of progression
This mechanic is required to fufill one of the core pillars. And therefore we must continue to work on it.

- US-11: As player I want to be able to use emotes to interact with other players so that I can make meaningful connections
This mechanic too is a requirement for one of the core pillars of the game and therefore must be finished.

- US-12: As a player I want to be able to build structures to help defend my base more easily
This is an extra feature. It is close to finished but will go back into the product backlog, and is unlikely to be finished.

- US-14: As a player, I want to a shop in order to build buildings or buy weapons
While this feature was originally part of our core design, it is also not necessarily a requirement for the game to be shippable. There it has been put back into the product backlog but will likely not be finished.

- US-17: As a player I want the enemies to drop currency so that I can buy items
As the shop will no longer be worked on in sprint 3, this is also no longer necessary.

Planning sprint 4:

Deze sprint gaat gebruikt worden om de onderdelen van ons examen die we onvoldoende hebben te verbeteren.

Dit zijn (als team) de volgende onderdelen:

  • Kerntaak 1: Werkproces 4: Test Software Beoordeling: Team: O Wie: Daan, Byron, Dirk & Guido. Een nieuwe usertest met minimaal 2x verschillende personen in de doelgroep. Dit wordt gefilmd De vragen worden vooraf opgeschreven. Er wordt een samenvatting uit opschrijven en daaruit komen minimaal 3 nieuwe User Stories voor deze sprint. 3 user stories als groep.

  • Kerntaak 1: Werkproces 5: Doet verbetervoorstellen voor de software Beoordeling: Team: O Wie: Daan, Byron, Dirk & Guido. Er komt een reflectie door het hele team op de huidige versie van de game die jullie nu hebben. Deze bevat: verbeterpunten, goede punten. Dit is dezelfde reflectie als in 2.3. Hier komen nieuwe user stories uit, iedereen gaat minimaal 3 user stories schrijven en daarvan 1 maken van hoe de game beter kan. Niet kijken naar wat jullie al van plan waren, echt concreet kijken wat er nu staat.

  • Kerntaak 2: Werkproces 3: Reflecteert op het werk Beoordeling: Team: O Wie: Daan, Byron, Dirk & Guido. Er komt een reflectie door het hele team op de huidige versie van de game die jullie nu hebben. Deze bevat: verbeterpunten, goede punten. Dit is dezelfde reflectie als in 1.5. Er komt een reflectie door het hele team op het proces & samenwerking. Deze bevat: verbeterpunten & goede punten.

We zullen meteen van start gaan met K1W5 en K2W3, dus we gaan gezamelijk overleggen over onze samenwerking en de staat van de game. ook gaan we de game gezamenlijk spelen en noteren wat ons opvalt. Vanuit dit overleg en testing komen afspraken en userstories.

Op Maandag 3 Juni zullen wij 2 usertests afnemen

Sprint planning sprint 5

Deze sprint zal gebruikt worden om alle game-breaking issues te fixen die vorige sprint zijn onstaan. Ook zal er gewerkt worden aan het refinen van features en het fixen van issues die genoemd werden in de playtests. Ook zijn er dingen die we zelf graag beter willen hebben.

Er zullen alleen kleine features worden toegevoegd die problemen oplossen die veel terugkwamen in het usertesten. De sprint bevat dus grotendeels bug- en andere fixes. We plannen deze sprint wat kleiner in dan onze vorige sprints zodat we echt de tijd kunnen nemen om al deze issues nu echt uit de game te halen, zodat we niet later weer tegen deze issues aanstoten.

Userstories

The following userstories have been added to the product backlog (See Reflection and Usertest page for reasoning):

  • US-27: As a player I want my projectiles to shoot straight towards the position of my cursor so that I can be accurate with my shots.
  • US-28: As a developer I want the castle walls to have proper colliders so that the players cannot walk trough them.
  • US-29: As a player I want to be clearly able to see everything happening around me so that I can react.
  • US-30: As developer I want the experience bar UI to be uninteractable as it should only move up if the player gains experience and nothing else.
  • US-31: As a player I want to always face my mouse cursor so that I can aim properly.
  • US-32: As a developer I want the player to not be able to walk over objects as the player should always remain on the same Y level.
  • US-33: As the player, I want be able to change the player's class within the game, So I don't have to restart the game entirely.
  • US-34: As the player, I want the scene to be reset after the main base HP has been lowered to 0 HP, so the player can continue playing
  • US-35: As the player, I don't want to fall off the map, which also includes the enemies falling off, or fake players falling off so it won't softlock the game
  • US-36: As the player, I want a better way to see where I am and where the enemies around me are so I wont get lost in the game so easily.
  • US-37: As the player I want to know when I or the base takes damage via flashes or any other indicator so I wont die or lose without knowing
  • US-38: As a player I want the controls of the game to be made clear to me so that I don't have to search for them
  • US-39: As a player I want there to be more enemies around so that I don't spend most of the time looking for them.
  • US-40: As a player I want to easily be able to differentiate between allies and enemies so that I dont have to guess which is which.
  • US-41: As a developer I want the melee attacks to deal damage everytime so that the gameplay stays consistent.
  • US-42: As a developer I want the mockup players to have better behaviour to make them feel more like actual players and to make them feel more cooperative
  • US-43: As a player I want to be rewarded for reaching a new level so that gameplay feels rewarding.
  • US-44: As a player I want to be able to zoom the camera in and out to get a better overview of the game state.
  • US-45: As a developer I want to refine the animation system so that player animations feel a bit smoother
  • US-46: As a player I want to have variety between enemy types so that the gameplay becomes less repetitive.
  • US-47: As a player I want clarity about the goal of the game so that I immidiately know what to do.

###The following userstories were moved to the sprint backlog:

  • US-28: As a developer I want the castle walls to have proper colliders so that the players cannot walk trough them.
    • Small fix should be easily achievable in a short time
  • US-31: As a player I want to always face my mouse cursor so that I can aim properly
    • This heavily impedes gameplay and needs to be fixed.
  • US-32: As a developer I want the player to not be able to walk over objects as the player should always remain on the same Y level.
    • This breaks the game as the player and enemies cannot hit eachoter while they are on different Y levels
  • US-34: As the player, I want the scene to be reset after the main base HP has been lowered to 0 HP, so the player can continue playing.
    • This is a core requirement of the gameplay loop and needs to be fixed for the game to function at all. The functionality for this is also already available, it just got broken somehow.
  • US-35: As the player, I don't want to fall off the map, which also includes the enemies falling off, or fake players falling off so it won't softlock the game
    • This is a quick fix as it only requires the map border colliders to be ajusted to have no more gaps

###The following userstories have been completed:

  • US-27: As a player I want my projectiles to shoot straight towards the position of my cursor so that I can be accurate with my shots.
  • US-29: As a player I want to be clearly able to see everything happening around me so that I can react.
  • US-30: As developer I want the experience bar UI to be uninteractable as it should only move up if the player gains experience and nothing else.
  • US-33: As the player, I want be able to change the player's class within the game, So I don't have to restart the game entirely.

Clone this wiki locally