top of page

Catfuffle

Role: Game Designer, Artist
4 months 
Team of 4

This project showcases my ability to lead, create, and collaborate while developing an enjoyable multiplayer experience

 

Untitled1488_20250331131127.png
Ragdollcaticon.png

Game Summary

Catfuffle is a chaotic 2-4 player PVP party game where players take on the role of mischievous cats battling atop a multi-tiered cat tower. This game prioritizes unpredictable and humorous player interactions over competitive intensity. Players must navigate the tower, jump, push, grab, and avoid hazards to stay in the game.

Design Constraints

  • Chaotic Interactions Over Winning – Silly, unpredictable moments drive the experience rather than serious competition.  

  • Lighthearted and Playful Tone – The game should be fun and relaxing, never frustrating.  

  • Low Barrier of Entry – Simple mechanics allow anyone to pick up and play easily.  

This project showcases my ability to:

  • Project Management – Keeping a team on track, leading meetings, organizing workflows, and ensuring deadlines are met in a year long project, Helping team members integrating Jira into their workflow

  • Game Design – Developing mechanics that support a fun and memorable player experience.  

  • Art & 3D Modelling– Crafting visuals that enhance the game's theme and player immersion.  

Capture.PNG
image.jpg

Feature Ownership & Discipline Leads

To support efficient development and iteration, our team assigned feature owners and discipline leads across design, art, and engineering. Each feature owner was responsible for driving a mechanic or system from concept through implementation and iteration, while discipline leads ensured consistency and quality within their domain.

This structure helped us:

  • Maintain clear ownership and accountability

  • Reduce bottlenecks during sprint development

  • Allow parallel work without losing cohesion

  • Iterate on features more effectively during playtesting

By combining Scrum with defined ownership, the team was able to move quickly while keeping the game aligned with its creative goals.

Process

​​We followed an agile Scrum framework, organizing our development into five sprints across two major milestones.
Sprint 1 – Character Movement

In the first sprint, we focused on establishing a strong core movement system. The goal was to create simple, intuitive controls that anyone could pick up and enjoy. This also included the character design animations and SFX to signify the movement

Sprint 2 – Character Interactions

We implemented interactive mechanics that would define the game’s chaotic feel: grabbing, slapping and throwing. Sound effects and visual signifiers were added to enhance the feel of grabbing, slapping, and throwing.

Sprint 3 –  Multiplayer

Recognizing that multiplayer was a foundational feature for all upcoming mechanics, we decided to prioritize it earlier than originally planned. In this sprint, we integrated local multiplayer and created the controller inputs

Sprint 4 – Tower Design

We built a fully playable level Including 3 different types of obstacles; a spiky hairbrush, a bounce cushion and some pitfalls in the level

Sprint 5 – Scoring System

To bring structure to the chaos, we added clear win conditions. Players earn points by knocking others off the map or into hazards. This also includes players respawning to allow for replay ability.

Agile Scrum Workflow

Due to the project’s long development timeline, our team used an Agile Scrum framework to support frequent testing, iteration, and scope adjustment. Development was structured into sprints with clearly defined goals, allowing us to regularly evaluate mechanics, balance chaotic interactions, and refine player experience based on playtesting feedback.

Scrum enabled:

  • Consistent iteration on core mechanics

  • Early identification of design issues

  • Clear communication across disciplines

  • Flexibility to reprioritize features as the project evolved

This approach ensured that Catfuffle remained playful, stable, and enjoyable throughout its extended development cycle

bottom of page