Released: (23/05/23)
This was a team project made during a module at Abertay University and was overseen by members of Hyper Luminal Games, who provided consistent feedback on the project.
​
My role for the team in this project was: Producer / Programmer.
What Did I contribute?
My contributions to the team was setting up and organising tasks and documents for the team to ensure that the team was on track with the development of the game. Some of my tasks included:
- Updating a Jira page with tasks.
- Writing dev logs.
- Writing up Scrum meetings.
- Emailing and updating the client on developments.
- Ensuring the team is on track using the planned and wrote out schedule .
- Planning for potential issues that could arise.
- Some development on the game. Including some programming, and writing out of dialogues.
What is Nancy Glue?
Nancy Glue, is a Noir detective story seen through the eyes of a child, staring themselves and their toys in the case of the silver screen scandal.
​
This game is a 3D first person perspective hidden object game with a heavy focus on narrative and logic puzzles. As the player you must interrogate and question characters to unravel the mystery of the missing film reel.
​
The art style of the game utilises a 3D environment and blends this with some 2D elements for characters, set dressing and interactable items, these elements are part of the child's imagination.
Production Documents:
JIRA:
The below images detail the Jira page that was made for tracking our progress and tasks in sprints. It allowed the team to break the project down into smaller sized tasks that could be assigned to the relevant team member and dealt with in a specific time frame. The Jira page was updated over time and was iterated to make the system of completing tasks more understandable and functional, this helped quite a bit and made the process of completing and organising tasks easier and quicker for all team members.
Production Timeline:
The production timeline was a way to estimate where the progress on the game should be at. It was updated consistently in advance of the current week to give the most accurate plan of what should be done when. The reason for the production timeline's updates was to keep the project as on track as I could and to help plan time for issues, changes in schedules etc.
Initial picture of production Timeline in week 1.
Developed and re-configured production timeline from week 8 of development.
Finalised accurate production timeline from week 13.
Initial picture of production Timeline in week 1.
Meeting Minutes & Devlog:
The meeting minutes was a place to document what had happened on each session that we met up to discuss our progress that we had made. We had usually three meetings every week with in some cases having more if required. The meeting minutes acted as a place to record the progress made in that meeting and what needed to be done next meeting alongside any issues, interesting happenings or comments on the game and its progress.
Other Documentation:
The following Images are of various other documentation throughout the project. The first three images are of a risk assessment done for the project and relative to the projects needs and potential realistic issues, the first image shows the matrix that is used to calculate the risk of the issues that appear in the next two images. The final two pictures are of a data collection form made for gathering opinions and views on the game during testing sessions. Players were asked to fill these out so that we could update and make the game more balanced and fun. The Data collection form was split into different sections: Controls, Dialogue, Rating etc.
Simple Risk assessment Matrix developed to help me assess the potential risks and their impacts during development.
Part of the Risk Assessment document that outlines some of the potential issues that could arise during development.
Example of some of the types of questions asked on the form.
Simple Risk assessment Matrix developed to help me assess the potential risks and their impacts during development.
Bug Testing and Documentation:
Alongside Jira a separate document was made so that I could further keep track of the bugs we encountered in an alternative space. Jira was the main area used for bug tracking however this document allowed us to pass onto our lectures the bugs found.
The front page of a separate document used for detailing and documenting all the bugs found and their status.
Details of some bugs found within the game and their details / status.
More detailed bugs and their status from the known bugs document.
The front page of a separate document used for detailing and documenting all the bugs found and their status.