Agile and sprint plans

This week I planned out the tasks needed for the sprint. Using the requirements, Gantt chart and monthly tasks I have been keeping a track of current tasks to complete on hand. It is now sprint and I have fallen a little behind schedule, which has now resulted in shifting all current tasks to make room for completing a higher priority one. This is because a playable initial prototype is to be released in time for end of December time/ First few weeks of January to receive feedback. Mechanics which have been put on hold are as follows: - Interactable objects

- Scriptable cat

- Cat book - Personality - Bait cooldown

As a higher priority in order (agreed to showcase and implement animations for the interim demo in January with supervisor) animations have now been moved up and limiting key press for bait has been put on hold. Other elements are also needed for the interim demo such as adding a win state, a lose state and fixing any bugs. As a persona goal I had decided to implement some multiplayer functionality (which I have already started by this point) in the game and being able to switch modes.

The Gantt chart and all previous sprints were planned initially to complete everything by December in order to have leeway for other assignments in the seconds teaching block. Below is the current burndown chart. I had recorded the hours worked on the game so far per week and inputted them into a chart. This helps me keep an eye on how far behind I have fallen. The ideal hours per week is not realistic and so there were bound to be adjustments to be made and difference in the actual hours worked. There is however a slight drop in the estimated hours.