Introduction
In Lichgate you step into the robes of a powerful mage determined to halt the relentless hordes of undead. Harness and grow your magical abilities as you obliterate thousands of monsters, creating game-breaking synergies that turn the tide of battle.
Project Information
Roguelike, Survivors
Coral Engine
10
PC & Playstation 5
8 Weeks (April 2024 - June 2024)
Genre
Engine
Team size
Platform
Duration
Responsibilities & Contribution
On the right you have the Macro Design for this project I created this together with the leads. We made sure that everything was included. And this was our initial plan. If something had to be changed we discussed this in-depth, and made sure that the right changes could be made.
This helped the team a lot to stay on track throughout the project, and was constantly revisted.
When I joined the team, they already had a few foundational elements in place, so my first priority was to get up to speed especially with tools like Github and its integrated Scrum system, which I hadn’t used before. I quickly learned the platform, and made sure to talk to other Producers that were using the same tools in order to share the knowledge we had learned.
From there on I would attend all of the meetings to create some oversight. I acted as a mediator in discussions, ensuring everyone had a voice and that important insights were captured. I was also the notetaker in these discussions and also in our playtests, processing them so that the entire team had a clear, and accessible record of our decisions, and any outcomes that came out of it. This helped create continuity and kept everyone informed of any decisions that were made, allowing the team to stay consistent and informed.
Takeaways
I made sure I was always approachable. I would often make time to see what everyone was up to. Being engaged with the project like that made it easy for the team to approach me.
I loved talking about the design of things, I always made sure I was approachable and that everything stayed clear for the entire team.
I learned that Scrum is not always the best method all the way through. And that it is okay to change methodologies whenever that is required by the team.