Agile Planning - T3rabyte/Examen GitHub Wiki

Agile Planning - ACCESS DENIED

Trello: https://trello.com/b/HAegNzcN/examengroepje03

Project Overview

The goal of this project is to develop a game that raises awareness about cybersecurity within the Municipality of Amsterdam. The game will simulate real-life cybersecurity scenarios and provide players with interactive challenges to test their knowledge and skills. The gameplay will involve answering true or false questions, forwarding or deleting emails based on their maliciousness, and facing consequences for incorrect answers. Players will earn points for correct answers and the game will include a time limit. Additionally, there is a possibility to add a multiplayer mode where one player acts as the hacker.

Sprint Planning

Sprint Goals

Each sprint has a goal, following are some examples:

  • Develop the basic game mechanics and user interface
  • Implement the true or false question system
  • Integrate the email management functionality
  • Design and implement consequences for incorrect answers
  • Implement the point system and game timer
  • Prepare for the possibility of adding multiplayer functionality in the future

User Stories

To know what needs to be done make userstories. following are some examples on how to do this:

  • As a player, I want to be able to answer true or false questions to test my knowledge of cybersecurity.
  • As a player, I want to receive feedback on whether my answers are correct or incorrect.
  • As a player, I want to be able to forward or delete emails based on their maliciousness.
  • As a player, I want to face consequences such as screen freezing or popups for incorrect answers.
  • As a player, I want to earn points for correct answers.
  • As a player, I want to see a countdown timer to track the remaining time in the game.
  • As a developer, I want to prepare the codebase for future multiplayer functionality.
  • As a player, I want the option to play the game in multiplayer mode, where one player acts as the hacker.

Tasks

  • Set up the project structure and version control on GitHub.
  • Design and implement the game mechanics and user interface.
  • Create a question bank and implement the true or false question system.
  • Develop the email management functionality, including forwarding and deleting emails.
  • Design and implement consequences for incorrect answers, such as screen freezing or popups.
  • Implement the point system and integrate it with correct answers.
  • Add a countdown timer to track the remaining time in the game.
  • Refactor the codebase to accommodate the future multiplayer functionality.
  • Document the project, including setup instructions and gameplay guidelines.

Sprint Review

The sprint review will be conducted at the end of each sprint to evaluate the completed features and gather feedback from stakeholders. It will involve a demonstration of the game's functionality, followed by a discussion about any necessary improvements or adjustments.

stand-ups and stand-downs

Well executed standups and stand-downs can make it clear to everyone in the team who is working on what, what their progress is, and what has been done for the day.

Sprint Retrospective

The sprint retrospective will be held at the end of each sprint to reflect on the team's performance and identify areas for improvement. It will involve an open discussion about what went well, what could have been done better, and actionable steps to enhance the development process in future sprints.