Projectplan: Strange Galactic Friends
Date: 29.10.2024
Introduction
This document holds key-information regarding the development of the game "Strange Galactic Friends". It contains information like the way Tasks-progress is measured, the different milestones of the project and the different team members and their respective roles.
Project Organisation
The Team consists of five members.
Name | Role |
|---|---|
Gollwitzer Jannis | Primary Developer / Secondary Project-Manager |
Hirschberger Konstantin | Primary Project-Manager / Secondary Tester |
Hoffmann Jonas | Primary Architect / Secondary Developer |
Köster Luca | Primary Game-Designer / Secondary Architect |
Schmid Georg | Primary Tester / Secondary Game-Designer |
While the members have chosen certain roles, that does not mean they will only be doing work in that field. All Tasks can be completed by everyone, the responsibility for a Task lies in the person leading that field of work. They have the duty to oversee and quality-check Tasks in their field.
Project Practices and Measurements
All management related things will be documented in OpenProject.
The Project will be iteratively developed, following this structure:
Iterations represent the topmost layer. They represent a 3 week phase, in which certain Milestones are to be completed. In these 3 weeks all development should be completed 6 days prior to the end. Then there will be a quality check to see if the original developer missed something, this is supposed to be done 4 days prior to the end. This leaves room for bugfixes, replanning and other unforeseen circumstances.
Milestones are a bundle of Tasks that mark the completion of a certain group of features or an artifact. Each Milestone belongs to a certain field of work, meaning a certain member will be accountable for its completion and quality.
Artifacts are a special type of milestone that have a (physical) object at the end of completion.
Tasks are small features or a part of an artefact. These will be assigned to a member and have an accountable member. These will have a estimated work-time and an actual record of man-hours spent on it.
Bugs are issues that have occurred, but couldn't be completed at the time of appearance. They are high-priority and any member can fix them.
To track progress each member of the team will be giving feedback on their current development-progress each Tuesday and Thursday. If it is clearly visible that deadlines cannot be met, additional members will be assigned to help, unless the problem lies within the task itself, in which case a thorough discussion will be held.
Project Milestones and Objectives
| Iteration | Primary Objectives | Timezone |
|---|---|---|
| I1 | - Simple Level Prototype - Level Design - Player Design - Navigation Prototype - Testconcept | 05.11.2024 - 26.11.2024 |
| I2 | - HUD - Level Completion - Cave Levels - Major Refactoring - Storytelling - Playtest - Enemies | 27.11.2024 - 17.12.2024 |
| I3 | - User Interface - Sound Design - Creating Levels - Cutscenes - Polishing Wiki Formating - Gameplay Features - Tests | 18.12.2024 - 21.01.2025 |
Deployment
TBA
Lessons Learned
TBA