Sprint Meetings - wits-bezos/witsiemon GitHub Wiki
Sprint 1
Sprint Planning Meeting 22/02/2019
Proof Of Meeting
We discussed the product backlog for our first sprint. We will use the open-source Tuxemon app as a baseline. We agreed to start off with designing the map of Wits and importing it into the app. We will then add creatures. We have decided as a team to leave the GPS Integration for the second sprint. The points system will be left for the 3rd sprint. The databases and networking aspect will be handled in the 4th sprint.
Daily Scrum Meetings
Please feel free to have a look at our whatsApp conversations on the whatsapp folder
Product Backlog Meeting 27/02/2019
The product owner noted that he needed the Tuxemon game integrated into android first. Secondly he wanted to see a GPS program that displays the address, co-ordinates and near by places of the user holding the Android device. This box would be placed on-screen and would be visible at all times during the game.
Thus the map will be left for the second sprint.
Sprint Review Meeting 08/03/2019
After numerous attempts to compile the apk file for Tuxemon, the team and product owner have agreed to focus on the GPS and on similar open source games to Tuxemon, such as OpMon. The details to this new adjustment will be clearly stated after the next Sprint Planing Meeting.
Sprint 2
Sprint Planing Meeting: 13/03/2019
We met with our Product Owner, Steve, on the 13/03/2019, for our second Sprint Planing Meeting. We revised our product backlog and added new items to it. It was agreed upon that the compiling of the android apk file was a difficult task due to its outdated nature. Thus it is better for us to focus on this in later sprints.
The focus for the second sprint is to have the game working on windows with an updated wits map. Tuxemon will still be used as the baseline code. We also have to setup a database that talks to the game by receiving and submitting any game data requested by the game. All player data (i.e points, events, player stats etc.), is to be stored in this database.
We also need install an events system, that a player can intact with and hence create a more engaging story-line with in the game. There will be a number of events created by the development team. The events must appear to be random during the game play. The events will be stored on a file located on the server, the game should be able to communicate with this server by randomly selecting an event and placing it in game.
By the end of this sprint, there should be a small box on the screen, of the game, displaying data stored on the database. Events should occur, at random times, during game play. And the map should look similar to the wits main campus map.
Daily Scrum Meetings
Please feel free to have a look at our whatsApp conversations on the whatsapp folder
Product Backlog Meeting 11/03/2019
Updated Taiga Product Backlog list
Sprint Review Meeting
The initial route taken to code the game was a complete failure due to the outdated nature of Tuxemon, the Scrum Team decided to go with a different approach. This will be discussed in more detail during the Sprint Planning Meeting.
Sprint 3
Sprint Planing Meeting: 08/04/2019
We met with our Product Owner, Steve, on the 08/04/2019, for our third Sprint Planing Meeting. We revised our product backlog.
Since some parts of the Tuxemon game refuse to work, the development team will be focused on re-writing the code line by line, so that we can identify errors in the code as well as update any outdated code and links that may exist.
The database, GUI and events system tasks will be adopted from second sprint and completed within the third sprint. By the end of this sprint, there should be a small box on the screen, of the game, displaying data stored on the database. Events should occur, at random times, during game play. And the map should look similar to the wits main campus map.
Daily Scrum Meetings
Please feel free to have a look at our whatsApp conversations on the whatsapp folder
Product Backlog Meeting 20/04/2019
Updated Taiga Product Backlog list
Sprint Review Meeting
We managed to complete the GUI. However the events trigger on Tuxemon was not available, as well as the battle system. It was suggested we drop Tuxemon and write the code from scratch using YouTube Tutorials.
Sprint 4
Sprint Planing Meeting: 06/04/2019
The team decided to re-write the entire code, with the help of various YouTube tutorials, since Tuxemon contains to many missing files and extremely outdated code. The database, GUI and events system will be pushed to next sprint, after the completion of the Witsiemon game-play
Daily Scrum Meetings
Please feel free to have a look at our whatsApp conversations on the whatsapp folder
Product Backlog Meeting 20/04/2019
Updated Taiga Product Backlog list
Sprint Review Meeting
The Product Owner stated that he was "happy" with the current output of work. He noted that the project was indeed a very difficult task but was impressed with the way we want around problem and came up with a solution.
