This repository contains the code and a wiki that contains documentation about the project. exam for team 05
This project is for our final examen and our client is Paladin Games. The idea is to create a local co-op game where you need to work together to reach a common goal.
Our idea is to create a co-op puzzle game where you need to work together in split rooms and use light as the mechanic to solve puzzles.
| Build status |
|---|
 |
| Developers | Artists | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
| Type | Description |
|---|---|
Features |
View per-feature documentation |
Agile planning |
Trello board containing product & sprint backlogs, sprint plannings |
Asset convention |
Convention for all art assets |
Functional design |
Contains information on game design and the decision making of it |
Technical design |
Contains specifics on technical aspect of our game |
Code convention |
Code convention for C# and Unity |
Version Control Convention |
Convention on the use of git and how to work with it |
Folder structure |
Project folder structure |
Usertest |
Contains usertest footage of our game |
Daily Scrum |
Daily stand up and down |
Feedback Sprint review |
Feedback of each sprint |
Sprint refinement |
Refinment document checking what is left in the trello |
Sprint retrospective |
Retrospective document on each sprint retro |
Sprint Planning |
Document on each sprint planning |
| Type | Description |
|---|---|
| Sprint 3 Retrospective + reflectie | Reflectie op sprint 3 en het hele product vanaf sprint 3 |
| Usertest plan van aanpak | Een plan van aanpak voor de usertesting |
| Usertest feedback | Feedback en conclusies van de usertesting |
| Sprint 4 planning | Sprint 4 planning onderbouwen door de feedback van usertesting |
| Sprint 4 Trello board | Sprint 4 trello board met alle userstories van sprint 4 planning |
You can also browse our documentation via the wiki.
Readme is subject to change if any nessicary changes are required.