Workflow – AGILE & Sprints
The Agile workflow is built on an iterative process of continuous sprints, each with a clear objective. Before every sprint begins, we establish a plan outlining what will be executed, ensuring that each cycle delivers a more developed version of the game that represents a distinct part of the overall experience. As development progresses, later sprints may shift from specific feature goals to broader refinements, focusing on polish, balance, and cohesion across the project.
With a total development timeline of approximately 12 weeks, we will structure the project into two‑week sprints. At the start of each sprint, we will meet to define clear deliverables, ensuring that tasks remain focused yet adaptable to the evolving state of the project.
User Testing Practices
As part of our sprint‑based development practice, we will conduct a playtest within each sprint. Early sprints will focus on testing specific mechanics and design elements, allowing us to gather targeted feedback and identify issues at an early stage.
These playtests will primarily be conducted in‑house and kept small in scale, ensuring rapid iteration. Later in development, we will expand to larger exhibitions, where the emphasis shifts from individual mechanics to evaluating the overall player experience and cohesion of the game.
Platforms & Tools
| Names of Software used | Used For |
|---|---|
| Unity | Game Engine |
| Discord | Communication |
| Trello | Organisation and planning |
| Notion | Holds this Game Project Proposal so we can refer back to |
| Blender | 3D modelling assets |
| PowerPoint | For when we need to present our games |
| Procreate | Concept art |
| Google Form | Primary research for conducting surveys and receiving feedback |
| GitHub | Version control |
| Substance Painter | Texturing |