Project Plan
Project Information
RUIN GAME
Authors:
Aapo Hyyryläinen
Anssi Jämsén
Mikki Salo
Patrik Kaunisto
Teemu Kosonen
Terms and Abbreviations
References
| Reference | Material |
|---|---|
| HLTP | High Level Testing Plan |
| GDD | Game Design Document |
Project Contents
Introduction
The following document aims to explain the course of action, communication, conventions and staff for a third-person roguelite fantasy game RUIN.
Project Background and Objectives
The project is a game demo, which is developed during the Ticorporate/Demo lab study unit in Jyväskylä University of Applied Sciences. The project will be released internally for JAMK. \
End Products
- Project Plan
- Game Design Document
- Sprint Backlog
- Game Demo/Proof of Concept
- Product Trailer
Project Qualifications
The passing project is the one that will be presented at the final demo day during the study unit, regardless of the state of the game.
MVP
- Core gameplay loop can be played through (New Game -> Select class -> Beat level).
- 3 classes with their respective abilities/skills.
- Classes use the same base model.
- 1 level with boss fight
- 10 artifacts with status effects.
- 1-2 enemies (melee, ranged).
- 6 different rooms + boss room.
- Basic UI and menu. Feat system.
- Two soundtracks, ambient and boss music, in-game sound SFX.
Plan of action
Scrum framework will be used for the project.
The status of the project will be tracked in ZenHub or Trello depending on the plugin availability. This will be also used for task management in the form of product backlog.
For documents and time management we will use the project’s GitHub directory, Office365 suite and Google suite.
Internal communication is handled in Discord between the project team, and communication with the organization will be done through Microsoft Teams.
Project Start
Project begins with creation of this document and initial version of the Game Design Document between 18.1.2021 and 31.1.2021.
Project Implementation
Implementation begins on 1.2.2021 with a sprint planning session according to the scrum framework. The sprints will be 2 weeks long. The following meetings will be held on specific time frames:
- Daily scrum
- Sprint planning
- Weekly meeting
- Sprint review + Retrospective
Additionally backlog grooming will be done when there is a need for it.
Project Testing
Project Testing is described in full detail in the High Level Testing Plan. Overall testing will be done using technical demos and content produced during the project.
Project Ending
The project will end in bankruptcy on 12.5.2021.
Project Resources
Work Groups
| Name | Roles | Contact |
| Teemu Kosonen | Scrum Master, 3D waving of the arms | N3957@student.jamk.fi |
| Anssi Jämsen | Product Owner, Content Creation | H9282@student.jamk.fi |
| Patrik Kaunisto | Content Creation, TikoBiz | N1361@student.jamk.fi |
| Aapo Hyyryläinen | Developer, Testing | L7034@student.jamk.fi |
| Mikki Salo | Content Creation, Developer | N3261@student.jamk.fi |
| Ville Kolu | Programming | gr200924@gradia.fi |
Stakeholders
| Name | Roles | Contact |
| Teemu Pölkki | Lab Director | teemu.polkki@jamk.fi |
| Jukka Riikonen | Coaching (PO & SM teams) | jukka.riikonen@jamk.fi |
| Riikka Ahlgren | Business | riikka.ahlgren@jamk.fi |
| Risto Koskenkorva | Product coaching | risto.koskenkorva@jamk.fi |
| Ilari Miikkulainen | Narrative, Marketing | ilari.miikkulainen@jamk.fi |
Tools
- Unity 2019.4.18f1 (Long Time Support)
- Cinemachine
- RealToon
- Universal Render Pipeline
- ProBuilder
- ProGrids
- TextMeshPro
- Post Processing Stack v2
- Collaboration
- Animation Rigging
- FMOD
- git & GitHub
- Visual Studio and/or JetBrains Rider
- Blender
- Vroid Studio
- Substance Painter, Designer or Quixel Mixer
- Adobe CC (Photoshop, Illustrator, Premiere Pro)
- Krita or Clip Studio Paint or Corel Painter
- Google Suite
- OBS
- Discord & Teams
- OneDrive & Google Drive
- Reaper
- FMOD
- Flinga
- Trello (GitHub, Scrum for Trello, Burndown for Trello) or ZenHub
- PureRef
- Windows PC
- Graphics tablet/screen
- Microphone
Timetable
| Event | Date | Additional information/Participants |
| Preproduction Begins | 18.1.2021 | Online meeting space, Full work group. |
| Initial sprint | 1.2.2021 | Online meeting space, Full work group |
| Demo #1 | 25.2.2021 | Online meeting space, TIKO students |
| Demo #2 | 1.4.2021 | TBD, Online meeting space, TIKO students |
| Demo #3 | 12.5.2021 | TBD, Online meeting space, Unknown |
| Project ending | 12.5.2021 | Unknown |
Reporting and Communication
Internal Reporting
| Name | Role | Responsibilities |
| Teemu Kosonen | Scrum Master | Scrum related reports (Sprint planning, sprint review, retrospective) |
| Aapo Hyyryläinen | Developer, Testing | High Level Test Plan, testing schedules, bug reports. |
| Anssi Jämsén | Product Owner | Backlog grooming |
Communication Channels
The main communication channel for the project will be Discord. Every person has their own voice-channel, where they work, and where people can join to discuss matters if necessary. In addition, there is a general voice-channel for general discussion and meetings, and there are also text-channels for different subjects. Teams will also be used for communications.
Documentation Templates
- The meeting minutes will be done using templates provided by JAMK.
- The High Level Test Plan will be produced using the guidelines provided by JAMK.
- Bug reporting will also be conducted using templates and guidelines listed in the HLTP
Document Control
The documents will be held in a group’s shared OneDrive folder and the scrum master will hold backups of the documents on a personal cloud drive.
Scrum Plan
Daily Scrum
The daily scrum will be held after 15 minutes in the work day and it should be done in 15 minutes. All members of the team decide what they are going to do during this meeting, they will also tell what they have done since the last meeting and bring up any issues with their work.
Generally all scrum related activities require active participation from all team members.
Sprint Planning
Sprint planning will be held during Monday on the first day of the sprint. The time reserved will be 2 hours but can be extended if needed. The user stories that are selected during the sprint planning are to be completed during that sprint. Minutes will be produced from this meeting.
Sprint Review
Sprint review will be held during the last day of the sprint. The length of the sprint review will be limited to 1 hour. During the sprint review the Product Owner discusses the completed user stories and the team members will show the work that they have done during the sprint. Minutes will be produced from this meeting.
Sprint Retrospective
Retrospective will be held during the last day of the sprint. The time reserved will be 2 hours. The purpose of the meeting is to have open discussion about any issues, opinions, ideas and improvements related to the completing the project. Minutes will be produced from items discussed during this meeting.
Risk Management
| Risk | Probability | Impact | Prevention |
| The group members are not motivated and do not show up | Small | Large | Providing virtual coffee and buns |
| Inadequate ability to produce 3D assets in timely manner | Medium | Large | Asset flip |
To Be Determined
We currently work online, however we move to work on Jyväskylä Digi & Game Center as soon as it is possible.