CAGD ePortfolio

  In this second sprint, I think I can say our team was able to get some work done. The marketing team meetings really eat into class time, which is kind of annoying, but at least we are mostly out of the pre-production phase. The other people on the team still need some time to familiarize themselves with the project.   Meanwhile, our programmer went to work on creating an “earthquake scheduler” scriptable object that could be used to plan out the earthquakes so that users could potentially create their own scenario and see how the earthquakes affect the map at certain times. I really like that the programmer made documentation even someone like me, a less than middling programmer, can understand. At the moment, we’re waiting for the earthquake data from the USGS scientists to come in so we can make sure that the scriptable object is accurate.   Our team had to meet up with the marketing team to talk about creating a new name for the game, as “Aftershock Forecaster...

  This semester, I am still the producer on the USGS Aftershock Forecast project. Despite being experienced on the project since I was on it last semester, it’s still no less nerve wracking than it was when I first started. Unlike last semester, we were actually able to have first-person talks and playtests with people from USGS.   One thing I considered unexpected was the type of people that would be brought into the project. I thought we would get another all-programmer team like last semester and continue what we were doing. But instead, we get a definite designer (although technically all of us can design) and just one main programmer. We are potentially able to have more programmers working on the project if the other teams have them free to do things. Although, we can never have enough programmers.   This sprint ended up being a pre-production phase, and our in class time was taken up by meetings with a marketing team. I remember the team being vaguely mention...