— PROJECT NAME
Chain Reaction
— ROLES
Lead-Programmer
Lead Level-designer
Game Designer
— DURATION
7 Weeks
— TEAM SIZE
5 People
Chain Reaction is a third-person, Local CO-OP platformer game. The objective of the game is to collaborate and coordinate in order to complete levels and win the game show!
This is one of the bigger projects during my studies. It was a great learning experience.
MY CONTRIBUTIONS
Developer
- Unity setup
- Code base
- Gameplay code
- Tutorial code
Designer
- Gameplay design
- Level design
- Tutorial Design
Scrum Master
- Made plans
- Created tasks
- Distributed tasks
- Organized team
Other
- Trailer
- Audio
- Music
GAMEPLAY
The goal of the game is to complete levels in order to progress and win the game show! The game includes 10 different levels with hazardous challenges. The game is also playable on both keyboard and gamepad.
MECHANICS
The game has two main mechanics
Chain
The characters have to be close enough to each other at all times to prevent the chain from breaking! This feature was intended to require the players to work together.
Coordination
Coordinating the characters is essential to be able to complete levels. Because walking away too far from each other will result in the chain taking damage.
CHALLENGES
Each obstacles in the game is meant to be unique and challenging for the player. Each level combines a new element to challenge the player.
LEVEL-DESIGN
To design levels for the game we utilized Miro. We used it to primarily brainstorm various level designs, which then was used as a template when building the level.
This was an effective method to help design the levels in the game.
SCRUM MASTER
As a scrum master, I took care of the backlog, choosing the agenda and coordinating workflow. I held daily scrums where I managed and distributed user stories (tasks) to designers and artists alike. We also used these opportunities to share ideas and thoughts. Furthermore whenever a user story was completed a new one would be assigned on the next daily scrum. To ensure that everyone always had at least one task, each team member received additional tasks to work on.
- Being a scrum master was a great learning experience, which taught me how to structure and plan projects with scrum. But most importantly how to communicate with the team to get everyone’s opinion.
A epic, with completed user stories and tasks.