CAGD 370

Sprints four is one of our busiest and most stressful sprints and I do not think sprint five will be any different. With the deadline for our prototype coming up we are definitely trying to make sure we have a working version before the deadline so that way the prototype is playable for others, and we do not fail the whole class. As a group we have decided that on December second, we would like to have a working version done by and also when we want the final build to be ready. As for how many points we have left for the prototype, we do not think anything will be cut as we are on track to finishing by our deadline. Sprints four and five are going to be some of our fist sprints where we had the right amount of work assigned at kick off and we had no incomplete work. Previously we would assign ourselves an extra user story on the last day because we needed to have something is assigned but this time, we did not do that, and we now know that we should have kept what we were doin...

  The Prototype is going really well, we have most of the hard part done in my opinion. I think that because I felt like, at least for me, getting our movement mechanics working properly was the hardest thing that I had to at least do for the prototype, and I feel like the next couple of sprints should go very smoothly. As a group we don't have much left to do and even on an individual level there is not much left, at least not much hard stuff, and we will need to add more for us to do or I think what we will do is just go back and refine and tweak and few things as so the game can run a little bit smoother . In the end we have not decided what we want to do. I think that we are going to wait until closer to the end of this sprint to figure out what we want to do. As the semester went on and we used agile development more I think we got a little more used to it and it also helps that our lead is on top of her work and what she needs to do as a lead. At the start of this sprint, we...

This sprint went very well. I feel like the whole group is starting to get used to agile development as a whole. I felt like I was able to appropriately give myself the right amount of work at sprint kick off and only a few things needed to be changed due to a change in the card's priority. While many other teams had to change some of their game in order to fit the requirements all we needed to do was add another movement mechanic to ensure that ours would be unique enough for the prototype requirements. The only thing that we did not understand was that we were able to throw cards back into the backlog, we thought that once a card was assigned that it was stuck in assigned until it was complete. Now that we know we can throw cards back into the backlog it will help with cleaning it up and making the higher priority cards easier to find later on. This sprint I was able to finish a good amount of work. I ended up finishing the player hand detach the day after we had our sp...

            The making of our prototype has been going well so far everyone has been doing their work and there have been no issues so far. This is my first time using agile development and I think it is also my teammates first time using it, so we are all trying to figure out how much work we can do within one sprint period. Personally, because I have never used this format before, figuring out how much work I can get done within one sprint period has taken me longer to figure out. It is taking me some time to figure out because my workload is changing week by week with my other classes while also trying not to burn myself out with just one class, because of this during the first sprint kick off I assigned myself to little work so I went back and had a couple more cards assigned but then was unable to finish both of them by the time the sprint was over.                         ...