Skip to content

Sprint 1

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

##Sprint Planning / Goals

Total Number of User Stories: 5

Total Time: 28 Hours

Research #1: Learn Unity - 8 Hours

Research #2: Design Decisions - 4 Hours

US 22 (Partial): Mosquito Functions - 4 Hours

  • Assigned to: Nida
  • Mosquito Movement
  • Mosquito Health
  • Mosquito Damage
  • Mosquito Hitbox
  • Mosquito Counter (How many die each time they are tapped)

US 23: House Setup - 4 Hours

  • Assigned to: Marcus
  • House Health
  • House Location
  • House Hitbox

US 28: Weapon Setup - 4 Hours

  • Assigned to: Russell
  • Starting Damage Value
  • Decrement Mosquito Health
  • Weapon Names

US 27: Health Bar - 3 Hours

  • Assigned to: Pedro
  • Player Health Count
  • Starting Value
  • Health Decrement

US 36: Game Over - 1 Hour

  • Assigned to: Pedro
  • Transition to Game Over

##Scrums

###4/4 Scrum

Russell

  1. Since the last Scrum I created some of our basic game objects, such as the mosquito and house, and started some basics scripts to make mosquito movement and started the base for the weapons script.

  2. For the next Scrum I aim to add touch functionality that will allow the mosquitos to receive damage and be removed from the game in time for the demo.

  3. The obstacles impeding my progress is the change in scripting from Unity 4 to 5. A lot of tutorials use the syntax and functions of 4, which are different in 5 and either unable to be used or need to be changed accordingly. I am also having difficulties getting the Android Studio emulator to test run Unity project apk builds.

Nida

  1. Since the last Scrum, I have practiced coding with Unity and have become more familiar with its functionalities.

  2. For the next Scrum, I plan to gather information about the Zika Virus in order to create the Information Page for our game. This page will be made in Unity as a scene.

  3. The obstacles impeding my progress is a way to condense the amount of data that is available on the Zika Virus in order to give the game player a short introduction to the illness rather than an in-depth summary of its symptoms and treatments.

###3/30 Scrum

Russell

  1. Learning about Unity has continued since the last Scrum, I’ve begun to look at video tutorials on scripting in Unity and began to try writing some example scripts based on touch inputs, which will be useful for the damage interaction in our game.

  2. For the next Scrum, I will continue to further my knowledge of Unity and begin to write some type of touch input for the weapon user story I’ve been tasked with.

  3. The biggest impeding obstacles are finding some better documentation for Unity in Android specifically, testing scripts which may need a better emulator, and considering what Unity files will need to be added onto our repository.

Nida

  1. Since the last Scrum, I have continued to learn Unity and Android as the other members of my team. No code has been implemented yet because I am not completely confident in all the material I have learned.

  2. Until the next Scrum, I will research more about the tools that our app requires in order to further the progression of the project.

  3. The obstacles that are impeding my progress are the lack of beginner tutorials available for learning Unity. Beginner tutorials would allow me to have a better understanding of the way Unity works

Pedro

  1. Since last scrum I wasn't able to do anything, I got a combination of personal problems and others courses works that didn't allow me to do so

  2. For next scrum I intend to have finish the study of the unity and also have some ideas about the design.

  3. At this scrum my only obstacles were lack of time.

Marcus

  1. Continued studies on Unity, no implementation yet since i want to make sure i understand it before doing anything.

  2. I will continue studying Unity until I come up with what I need. I will try to change it to a more practical study with more basic implementations.

  3. I think that the main obstacle is the way that I'm studying.

###3/28 Scrum

Russell

  1. As we have not had any previous Scrums, for the first Scrum, I began to learn Unity by going through some documentation and tutorials to understand the basis of how to use it.

  2. Until the next Scrum, I will continue learning Unity and begin to try out the SDK further, aiming to start coding in Unity.

  3. The obstacles impeding my progress are finding some more illustrative guides to Unity, as some of the documentation, tutorials, and general usage of Unity with Android is confusing at times.

Nida

  1. For the first Scrum, I attempted to learn Unity and its functionalities. Additionally, I explored how Unity works with Android.

  2. Prior to the next Scrum, I will attempt to implement code in Unity, specifically to produce movement in objects on the screen.

  3. The obstacles that are impeding my progress are my complete lack of knowledge of both Unity and Android. I don't have any experience in game programming, so learning these tools within an extremely tight time range is incredibly difficult.

Pedro

  1. This was the first scrum, on tuesday I began leaning a little of unity, I haven't done any other work later, only worked about one hour at this day

  2. I will not be able to do any work until next scrum, because I will have some lack of time at the beginning of the week

  3. The obstacles until now are the lack of knowledge in the unity platform and some personal problem that are taking some of my time, I believe that by march 31 I will have some time to go back to the work

Marcus

  1. As the first scrum, the focus was on understand how unity works on android.

  2. On the next scrum I will continue studying Unity and hopefully start some coding.

  3. The lack of knowledge on Unity is being the main obstacle so far, as I thought it would be a lot simpler.

##Demo & Retrospectives

  • Total Number of User Stories Planned: 5

  • Total Number of User Stories Implemented: 3

  • Total Time: 28 Hours

  • Total Time Taken: 40 Hours

  • Sprint 1 Demo Video

Code:

Summary: In order to create a successful product in an efficient time manner, the team should start communicating more often. Each team member should check slack a few times a day to make sure they are not missing important messages regarding the project. The team should also start organizing their time better. Since each of us carries the burden of responsibilities from our other classes, it is important to make a set time where work must be done for the project. This method of organizing time will allow a portion of the project to be complete during each scrum. In terms of what the team should stop doing, the team should stop trying to learn the tools all on their own. It is important to bring up questions concerning the tools we are using, especially Unity on slack. Instead of searching the internet for the answers to the question, another team member may be able to answer the questions, which will save time for the progression of the product overall. The team should continue to develop sections of the game during the sprints. As long as code is being developed and discussed among the team members, the game will be successfully made.

Burndown Chart for the Sprint:

Sprint 1 Burndown Chart

What Needs to Be Done:

  1. Touch input for the user to actually play the game
  2. More gameplay elements
  3. The menu scenes need to be created so the user can navigate through the game easily
  4. Background images need to be added to the panels
  5. Additional features that will be added to the game if time permits it include the Leadership board and the Gallery of Mosquitoes
Clone this wiki locally