Monitoring and Controlling

During the development of this game, the team has utilized many strategies to keep track of project progress and ensure that the project is on track. This section will outline these strategies used to monitor and control the project.

Monitoring Project Variables

Version Control with Git and GitHub

Branches and Commits

Regular commits were made to reflect project progress and ensure traceability. Branches were used to separate features and bug fixes from the main branch.

Issue Tracking

Issues were created on GitHub to track bugs, features, and enhancements. Each issue was assigned to a team member and labeled by type. Issues were closed when the task was completed. Labels such as To Do, In Progress, and Done were applied to track progress. This is utilized to communicate and organize the tasks for this project.

GANTT Chart

A GANTT chart was created to visualize the project timeline and track progress. This chart was updated regularly to reflect the current state of the project, and is on GitHub (this is slightly different from the Google Sheet submitted on Google Classroom). Due to unaccounted for scope creep, some project tasks were delayed, but the GANTT chart was updated to reflect this.

Communication

Direct Messages

Team members communicated through direct messages on Discord to discuss project progress, issues, and solutions. This was used to ensure that everyone was on the same page and to resolve any issues that arose.

GitHub Issues

GitHub issues were used to communicate and track project progress. Issues were assigned to team members and labeled by type. This was used to ensure that everyone was aware of the project’s status and to track progress. Once a new issue is assigned/edited to a team member, they will be notified via an email.

Conference with Supervisor

The team met with the supervisor to discuss project progress and suggestions to improve the game. This was used to ensure that the project was on track and to receive feedback on the project.

Corrective Actions Taken to Address Issues

Delays in Feature Completion

Due to unaccounted for scope creep and/or complexity, some project tasks were delayed.
To address this, the team met to discuss the issue and reassign tasks to ensure that the project was completed on time. The GANTT chart was updated to reflect the new timeline. In addition, some partners were assigned to help with the tasks that were delayed to ensure that the project was completed on time.

Unaccounted For Bugs

Some bugs were discovered during testing that were not accounted for in the project timeline.
To address this, the team created an issue in GitHub with a detailed description of the bug. Bugs were prioritized, so critical bugs were fixed first. Once the bug was fixed, the issue was closed.