General information

Development information

ENGINE

UNREAL 5

NUMBER OF PLAYERS

SINGLE PLAYER

GENRE

PLATFORMER

Awards

Dutch Game Awards 2023

Finalist Best Student Game

GDWC 2023 Summer Season

Finalist Made with Houdini

PROJECT DURATION

~ 10 WEEKS

BUas Industry Day 2023

Best Year 2 Game

PLATFORM

PC

4 PROGRAMMERS

10 ARTISTS

TEAM SIZE

6 DESIGNERS

Game Summary

The development of the game spanned a total of 10 weeks. It all began with a concept and a prototype, keeping in mind the unique constraint of creating a 3D Platformer. This early phase was critical for establishing the fundamental ideas and mechanics.

As the team brainstormed and experimented, a unique mechanic emerged: the "vault diving." Given the time constraints we faced, we transitioned into the production phase, putting our focus on bringing this mechanic to life and integrating it seamlessly within the gameplay.

Furthermore, a careful evaluation of the project's scope became crucial. We had to realistically assess the scale of the game and align it with the available workforce. Finally, we tackled rapid iterations through frequent playtesting, and between iterations we focused on bugfixing and optimization. This iterative cycle of testing, analysis, and refinement played a pivotal role in shaping the final version of the game, aligning it more closely with our vision and the players' expectations.

Viking Hiking was successfully released on Steam. It reached more than 40K downloads and earned a "Very Positive" rating from the community.

Responsibilities

From Concept to Release

Develop a Roadmap and a Milestones Plan for the project.

  • I developed a Roadmap, setting major goals and breaking them down into achievable milestones. To assign a realistic timeline, I had communication with all the developers, allocating the necessary resources and ensuring adjustment as the project progressed.

  • The challenge was to manage the scope based on deadlines and team capacity. So, I analyzed constraints and dependencies in pipeline development to avoid blockages and I had to make decisions based on risks evaluations and team capabilities to ensure that the project remains on track and achievable.

Scope Breakdown

Leadership and Communication

Direct communication with the team and the stakeholders

  • I maintained direct and constant communication and collaboration with the leads of each discipline. We updated each other regularly on task progress and any emerging issues. I organized both formal and informal one-on-one meetings with all team members to monitor satisfaction and involvement levels.

  • I pitched the concept and represented the team during stakeholder update meetings, acting as a link for updates between the team and stakeholders.

  • I actively participated in public events and enrolled the game for public awards. This enhanced our visibility and contributed to a notable increase in downloads. These events also provided the opportunity to conduct public playtests, gaining direct feedback from players. Additionally, I took on the role of a marketing manager, organizing a Marketing Plan, developing a community on Discord, compiling a competitor and press list, and personally managing the Steam page."

Gantt Chart

Gantt Chart

Project Management Methodologies

Responsible of Scrum and Agile methodologies

  • I defined the project structure and team organization through the development of a Team Contract and communication pipeline. The team was divided into strike teams with defined responsibilities and ownership.

  • As a team, we employed an Agile approach, specifically Scrum, which I adapted to the needs and characteristics of the team. For example, there was no Product Owner, but this responsibility was shared among the leads of the strike teams.

  • I created and owned the product backlog within the leads and kept track of progress throughout Sprints. We used Jira as the main tracking tool, so I onboarded the team to the use of the software and wrote documentation and guidelines about it.

Risk List

Main Takeaways

  • As a Producer, developing a roadmap and milestones plan is crucial for outlining the project's direction and key objectives. Managing scope based on deadlines and team capacity ensures that the project stays on track and resources are utilized effectively.

  • Being responsible for Scrum and Agile methodologies involves adapting these frameworks to fit the specific needs and characteristics of the team. This enables efficient collaboration, effective task management, and iterative development.

  • Onboarding the team to Jira Software and providing documentation and guidelines about it helps streamline project management and ensures everyone is aligned on the tools and processes used for task tracking and workflow management.

  • Identifying, preventing, and developing contingency plans related to risks is essential for proactive risk management. By anticipating potential challenges and having plans in place, the team can mitigate or address issues that may arise during the project.

  • Direct communication and collaboration with discipline leads allow for effective coordination and alignment among different areas of expertise. This facilitates a cohesive and synchronized approach to the project's development.

  • Conducting regular 1-on-1 meetings with team members helps monitor their satisfaction and involvement level. This promotes a supportive and engaged team dynamic, allowing for timely feedback and addressing any concerns or issues.

  • Setting up a QA pipeline and test plan documentation is vital for ensuring product quality. It involves establishing systematic processes for testing, bug tracking, and quality assurance to deliver a polished final product.

  • As a Community Manager, organizing a marketing plan involves strategizing and executing promotional activities to raise awareness and engage the target audience. Maintaining competitor and press lists helps stay informed about industry trends and opportunities.

  • Developing a community in a Discord server fosters a sense of belonging and engagement among players and fans. It provides a platform for communication, feedback, and building a dedicated community around the game or project.

  • Participating in public events and signing up for public awards increases visibility and recognition within the industry. It helps establish credibility and promotes the project to a wider audience.

Documents

Production Plan

I created a documentation to manage and organize the development of the project, as well as risks and a draft budget. It was helpful for me to be able to analyze at a macro and micro level what was planned so as to act promptly.

Jira Guidelines

I created these guidelines to help team members become familiar with Jira. I also adapted the content based on the specific situations and characteristics required.

Marketing Plan

I created a documentation related to marketing to identify the possible assets needed to be created. I also developed a competitor analysis to identify possible pros and cons of other products.

Feel free to contact me to get access to these documents!