Current Roles

Creative Director

• Hosts sprint retrospectives to discuss the most recent sprint.

  • I make sure that the team knows these discussions are open for anyone to provide feedback.​

• Verifies all work meets the discussed vision we have for the game.

• Manages discipline leads and sub-team leads to make sure the team is not only contributing to the project but learning along the way.

​

Lead Producer

• Frequently checks in with individual team members to ensure work is being completed as expected.

• Notifies team members that any/all of their opinions are valid and will be taken into consideration.

  • I want people to be excited to work on this project. I want them to take ownership of their work and feel like they are contributing to something amazing.​​​

• Makes sure the team is not only contributing to the project but learning along the way.

​​

Other Achievements​

• Created anonymous feedback form where the team can privately express concerns and considerations.

• ​Created and manages our ClickUp page.​

• Overhauled project management when work was not getting completed.

  • My efforts resulted in a steady flow of work being produced, increased communication between sub-teams, explicitly defined expectations for being a member of the project, a discipline lead, and a sub-team lead.​

​

Roles during Capstone

Core Gameplay Programmer on the Disasters Functional Team

• Refactored old prototype code to follow design principles and to be more expandable.

  • Utilizing inheritance and composition to create new disasters and methods of placing them in the game.

• Created backend architecture to streamline creation of new disasters.

• Created backend architecture to streamline creation of new disaster placement types.

• Created documentation to inform team members of how the system works, how to create new disasters, placement types, etc.

​

Analytics Tracking

• Setup a MySQLserver using phpMyAdmin to track analytics such as disaster usage, time spent per level, hazards interacted with, etc.

• Programmed C# scripts to collect and aggregate in-game data to prepare it for submission.

• Programmed PHP scripts to accept queries coming from the in-game database handler.

​

Documentation

• Disaster and Placement Creation

  • Created documentation to inform team members on how the system works, how to create new disasters, placement types, etc.

• Analytics Tracking

  • Created documentation to inform other programmers on how the data is being tracked, stored, and prepared for submission.

​

Presentation

• Originally made for the Game Design Club at Bradley University, I presented a PowerPoint I created on getting started with GitHub and best practices.

• Click here to view.

​