The work displayed in this repository will be done by the 38th Bootcamp team of Google's Game and Application Academy. The team member who's responsible for keeping this repository up-to-date is the Scrum Master.
TBD
-
Alperen Karaduman > Developer/Product Owner
-
Sevcan Doğruyol > Developer/Scrum Master
-
Sefa Cansever > Developer
Impossible Revenge
Our main character Allard has lost his family at a young hage. Unfortunately, due to the trauma caused through his parents' passing, Allard doesn't remember a lot about his past. He grows up with a royal family, who had adopted him when he was still so young. In his adult years, Allard joins the King's Army and rises to higher titles quickly, with all of the battle commendations he earns in the service of the Karovenj Kingdom. During a kill mission, personally bequested to him by his King, he comes into possesion of some vital information and thereafter begins his adventures.
- PixelArt Platformer Game
- Choice-based storyline
- Action Sequences
- Collectibles
- Possible hidden storyline
- Gamers, who enjoy historic storylines
- Gamers aged between 15-39
- Gamers, who enjoy less action sequence, more story-emphasis and user friendly platforms
Here, you can find the Miro Scrum Board for the Impossible Revenge game project. As long as you have access to this URL, you will be able to view the board.
- Sprint Notes: Story points and user stories have been explained product backlog entries. The details could be found in full entry mode.
- Possible Sprint Completion: 70 Points
- Backlog Orgnization and Story Choices: Product Backlog is organized to detail every feature that is predicted to be implemented to the product by the end of the 3rd Sprint. Stories were based on how the product could be made more appealing to the user with graphics, animation, asset quality and so on.
- Daily Scrum: In this first sprint, Daily Scrums were conducted on 3 seperate channels(ClickUp Chat, Whatsapp and Slack). From now on, they will be conducted only on Slack, barring any emergencies. The screenshots to said chats could be seen on the Miro Board.
- Sprint Board at the end of Sprint #1: Below you can see the screenshot of the end-of-Sprint board
- Product Backlog: Below you can see the screenshot of the product backlog
- The progress in the product as of the end of Sprint #1: Below you can see screenshots from the product's the latest condition
- Sprint Review: Since the team member responsible for AI study and C# scripting had to quit the Bootcamp towards the end of the first sprint and this development inevitably stalled the progress of our product, we've decided to work more hours in the coming two sprints to rectify our goals and catch up to our story points targets.
- Sprint Retrospective:
- The Daily Scrums need more discipline from every team member and efforts to remedy absences will be taken.
- Due to one team member's withdrawal from the project, as a four-people group, we need to revise the story points dedicated to each sprint.
- Sprint Notes: Story points and user stories have been explained product backlog entries. The details could be found in full entry mode.
- Possible Sprint Completion: 110 Points
- Backlog Orgnization and Story Choices: Product Backlog is organized to detail every feature that is predicted to be implemented to the product by the end of the 3rd Sprint. Stories were based on how the product could be made more appealing to the user with graphics, animation, asset quality and so on.
- Daily Scrum: As stated at the Sprint #1 report, the Sprint #2 Daily Scrums were conducted only on Slack (with the exception of few cases where Whatsapp was a means of communication with regards to push/pull requests, asset discussions and so on. It was decided to exclude the screenshots of these conversations from this report for a more formal outlook). The screenshots to said chats could be seen on the Miro Board.
- Sprint Board Screenshots: Below you can see the screenshots (1) the goal for the Sprint, (2) the circumstances at the end of the Sprint.
- Product Backlog: Below you can see the screenshot of the product backlog
- The progress in the product as of the end of Sprint #2: Below you can see screenshots from the product's the latest condition
-
Sprint Review: While we have improved on our work, we've decided that the last week of this Sprint was not as fruitful as we've hoped it to be. In the meeting of 21st of May, this issue was discussed and ways to rectify it in the coming Sprint were laid out by team members.
-
Sprint Retrospective: -Since this Sprint has showed what little time we've left could be crucial to creating an MVP, we've decided it would be best to manage our workload in a way that would be the most effective in the first week of the Sprint #3. This isdue to the fact that all members of the team, being students will prove the last week of the Sprint #3 to be very difficult in terms of collaboration.
Notes: The Daily Scrum Screenshots can be found in the same adress as they were in for the Sprint #1 report: https://miro.com/app/board/uXjVO2v4jX0=/?share_link_id=499352999756
- Sprint Notes: Story points and user stories have been explained product backlog entries. The details could be found in full entry mode.
- Possible Sprint Completion: 208 Points
- Backlog Orgnization and Story Choices: Product Backlog is organized to detail every feature that is predicted to be implemented to the product by the end of the 3rd Sprint. Stories were based on how the product could be made more appealing to the user with graphics, animation, asset quality and so on.
- Daily Scrum: As stated at the Sprint #1 report and the Sprint #2 reports, Daily Scrums were conducted only on Slack (with the exception of few cases where Whatsapp was a means of communication with regards to push/pull requests, asset discussions and so on. It was decided to exclude the screenshots of these conversations from this report for a more formal outlook). The screenshots to said chats could be seen on the Miro Board.
- Sprint Board Screenshots: Below you can see the screenshots of the (1) the goal for the Sprint, (2) the circumstances at the end of the Sprint.
- Product Backlog: Below you can see the screenshots of the (1) the goal for the Product Backlog, (2) the circumstances at the end of the Bootcamp.
- The status of the product as of the end of Sprint #3: Below you can see screenshots from the product's the latest condition
-
Sprint Review: Due to the workload we are facing in the last sprint, we decided that it would be best to focus our efforts on an MVP for the Academy's review. However, we plan to continue to collaborate in the future to improve our skills through this project and on the tools of collaboration.
-
Sprint Retrospective: As it was the case, and stated in the report of the Sprint #2, we've done our best to manage our workload in order to create an MVP. While we've had more ideas and a better imagination for our game, sadly mostly due to a teammate leaving our team at 5th week of the 6-week Bootcamp program, unfortunately without completing any of their assigned tasks we've struggled to create even the MVP that we would like to present to the experts of the Academy. However, we still value the remarkable lessons we've gathered from the Google's Game and Application Academy Bootcamp. And we are incredibly grateful for the value that this program has provided us with, through a first-time, hands on collaboration of an actual project from start to finish.
Notes: The Daily Scrum Screenshots can be found in the same adress as they were in for the Sprint #1 report: https://miro.com/app/board/uXjVO2v4jX0=/?share_link_id=499352999756
Thank you to the Academy employees and volunteers for their support and encouragement.