Skip to content

Sprint 2

Jump to bottom
rgee258 edited this page May 6, 2016 · 31 revisions

##Sprint Planning / Goals

Total Number of User Stories: 8

Total Number of Hours: 16

US 1: Welcome Screen - 2 Hours

  • Assigned to: Pedro
  • Create a main menu with different navigation options.
  • The buttons that would be displayed on the main menu are Play and the Settings options.

US 4: Pause Functionality - 2 Hours

  • Assigned to: Marcus
  • Create a pause functionality, allowing the users to play the game whenever they prefer to do so

US 17: Unpause Functionality - 2 Hours

  • Assigned to: Marcus
  • Create an unpause functionality, allowing the users to cease to play the game whenever they play to do so

US 28: Touch Input - 3 Hours

  • Assigned to: Russell
  • Add a touch input to the game, allowing users to eliminate the mosquitos on the screen by tapping on each one to gain points

US 3: Instructions Page - 3 Hours

  • Assigned to: Nida
  • Create the information Page for the Game, so that users can read about the Zika Virus and understand why the game is based on this disease

US 9: Background and Graphics - 2 Hours

  • Assigned to: Nida
  • Search for graphics to display on each screen throughout the game

US 27: Health Bar - 2 Hours

  • Assigned to: Pedro
  • Create a health bar to indicate the end of the game

US 24: Progressive Difficulty - 3 Hours

  • Assigned to: Russell
  • Add to the game with multiple mosquitos flying throughout the screen while the game is in progress

##Scrums

###4/18 Scrum

Russell

  1. Since the last scrum, I've managed to implement the touch functionality with the mosquitoes on the gameplay scene, added various spawners to the mosquitoes, enhanced the mosquito movement script so they move towards the house from any position, and allowed for the mosquito sprite to rotate towards the house appropriately.

  2. I've done the touch functionality and most of the base for the game progression user stories I've been assigned, so I'm planning on enhancing the gameplay a little more. Doing so would include fixing the health scripts for the mosquitoes and creating a plane for mosquito spawns rather than a single point.

  3. The biggest impediment this Scrum definitely had to be the touch input. I had some trouble figuring out the appropriate methods that needed to be used with it, otherwise what would happen is touching to destroy a mosquito would destroy all of the duplicate ones. Another would be the weird interaction with the health script, which I'm leaving to try and fix before the demo or figure it out, and possibly change it for the next sprint.

Nida

  1. Since the last Scrum, I have created the Help Page Screen for the game, which will be utilized in the case of users needing instructions on how to play the game. I have also added buttons for navigating between each screen in the game, whether it be from the Game Over screen to the Play Again screen or the Main Menu Screen to the Info Page Screen.

  2. For the next Scrum, I plan on reviewing the screens for the game, making sure that each one is working. During today's Scrum, our team discussed a few spelling and layout errors in the First Screen that displays the title of the game. I will make sure to fix these errors before the Demo in two days. I will also be setting the background for the actual game screen, where the mosquitos are attacking the house and the user must tap on each to remove them from the screen.

  3. The main impediment for this Scrum is working with methods in Unity. The methods that were most utilized during this Scrum involved navigating from one screen to another when a user presses a button.

Pedro

  1. Since last scrum I worked with Marcus in the stop button. However it got some problems when we added it with the new version of the mosquitoes movements
  2. For next scrum I’m going to fix the problem with the stop and the movements compatibility
  3. For this scrum I had the problem that the code changed during the development changing how we should do the pause functionality

###4/13 Scrum

Russell

  1. From the last scrum, I continued my research on touch input. I've learned that raycasts are some form of data structure used for touch interactions, but I'm currently unsure of how it works with Unity in 2D. I've also considered improving the game progression in ways using prefabs and multiple spawn points, but have yet to implement anything yet due to time limitations I noted in my last Scrum.

  2. For the next Scrum I have more time and look forward to implementation of touch inputs, potentially raycasts, and adding the objects needed to improve the game's progression. I'm looking forward to implementing most of my tasks for the next Scrum.

  3. The main impediment for this Scrum was my lack of free time for the project. I was unable to dedicate as much time as I wanted towards research and had no time for any implementation. I also need to make ensure my local repositories are in check with what is already on GitHub.

Nida

  1. Since the last scrum, I have gathered more graphics that will be displayed in the background for each screen on the app. I have also done research on how to create button components that will be displayed on the Information Page.

  2. For the next scrum, I plan on implementing the Instructions Page for the game. I have viewed other Help Screen Pages and have created a design for this Page. By the next scrum, this page should be created.

  3. The impediment for this scrum involves the issues I am having with Github.I am getting errors when attempting to add my changes to the project. In order to solve this issue, I will attempt to use another computer to add my changes to the project, so that my team members can view the changes that I have made to the code.

Pedro

  1. Since last scrum because of heath issues I haven’t been able to do any work

  2. For next scrum I plan to catch up in the health bar again

  3. unfortunately, I got health problems and wasn’t able to do anything and this was the biggest impediment for me.

###4/11 Scrum

Russell

  1. Since the last scrum, we began Sprint 2, and my tasks shifted towards touch input for the game and game progression having multiple mosquitoes. So far I’ve done some research into touch input to learn the touch data structure and have some idea of how to read in touches, but have yet to implement anything yet.

  2. For the next Scrum I plan on continuing research with touch input and look into how raycasts work, which may or not be needed for the game’s touch input. Additionally, I have the idea of improving game progression by adding spawns for the mosquitoes, but for now my focus will lie on learning touch input implementation.

  3. The biggest impediment for this Scrum and likely the next Scrum is going to be the amount of time available I have to work on the project. This week I have a lot of work for other classes that is taking up my time, so research may be done for my tasks for most of this week while implementation will likely be towards the weekend.

Nida

  1. Since the last scrum, I have worked on creating an Information Page that consists of facts about the Zika Virus. This part of the app also explains to users why the game was based off of the Zika Virus. I have also gathered graphics that will be displayed in the background for each screen of the app.

  2. For the next Scrum, I plan on researching ways to create a Help Page where users are given instructions on how to play the game.

  3. The impediment for this Scrum are the navigation functionalities. Even though I am creating different components of the app, they will only be displayed after being linked to the main menu where users will have the option of viewing these components.

Pedro

  1. At the this Scrum I worked on the main menu screen, I spend about 2 hours on it during the weekend and this part is almost done, just needing some design adjusts that will be done with time

  2. For the next scrum I plan to start on the health bar so if every think goes as planned it will be done by there

  3. I haven’t had any huge impediment for this task, however I don’t know how it will work with the health bar (My next work)

##Demo & Retrospectives

  • Total Number of User Stories Planned: 8

  • Total Number of User Stories Implemented: 6

  • Total Time: 16 Hours

  • Total Time Taken: 32 Hours

  • Sprint 2 Demo Video

Code:

Summary: Continuing from last our last sprint, although improved, we still need to improve our communications further. When we're working on specific tasks, we should notify each other of what we're doing and when we plan to commit so we have a more streamline scheduling idea amongst the team. We should also show each other graphics or upload them onto Slack before committing them so we can worry less about confusing commits. For what we should stop doing, we need to stop procrastinating when it comes to code commits. Although most of us are working according to our time alloted, we don't submit the more code intensive commits until the end of the sprint, and that has caused some mishaps this sprint. We should continue working at the pace we are in this sprint, as compared to the first sprint, we accomplished a lot for the basis of our game and it's navigation. While it's not perfect, it works as a rough state for where our game should be at.

Burndown Chart for the Sprint:

Sprint 2 Burndown Chart

What Needs to Be Done:

  1. Health bars
  2. Scoring of some type
  3. Improved and streamlined graphics
  4. Sound effects
  5. Additional game complexity
  6. Consideration of an exit button
  7. Script checking and potential condensing
Clone this wiki locally