Alex Chandler: CAGD 370

     This sprint went quite well, and we did not stumble on any major issues. There was a concern pointed out by our professor which I will be going into detail and exploring near the end of this post. The majority of the work done on this sprint was improving upon existing assets. This ranged from everything from level, to scripts, mechanics, and even our entire scene loading system. Because of this, there's no fancy level to showcase in this sprint. Despite not all our work being clearly visible this time around, take pleasure in knowing we spent the same amount of effort and work on changes that improve the game.  The first of the major mechanics we changed was regarding the player movement. This was pretty scarry as we already had six levels done, so altering anything regarding movement significantly could prove to make some of the levels unplayable and in need of a complete restructure. The reason we were looking into changing the movement system in the first place was that ma

 We just rapped up sprint 3 for Bedtime Climb, and so far things are still going smoothly. A new requirement that we have been given, and must me repeated now for every sprint, is creating a velocity chart. This entails writing down how many points we have completed over the past few sprints, and using a calculation to predict, using that data, when we would finish everything in our backlog. We currently have 110 points in our entire project, and have completed 35, 28, and 21 points over the respective sprints. Because of that, we only have 29 left, and our projected to finish the entire project by sprint 4. Of course I will be adding more cards to the backlog as we still need to be doing work during sprint 4 and 5. In the programming aspect of this sprint, we fell a little behind, hence why we only completed 21 points this sprint, while we're normally averaging 27. For what we have completed during sprint 3, was primarily 3 more levels. Level 3 was continued on from sprint 2 and f