From 603db3fe74db94ded146b22e9303dd8c064df494 Mon Sep 17 00:00:00 2001 From: Jaro Date: Tue, 10 Sep 2024 17:13:15 +0200 Subject: Added some risks --- plan.tex | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'plan.tex') diff --git a/plan.tex b/plan.tex index 55a6d12..43997f5 100644 --- a/plan.tex +++ b/plan.tex @@ -9,7 +9,7 @@ \newpage \section{Problem Definition} -The assignment is part of a fourth-year minor. The assignments are not set in stone to give the team an opportunity to discuss with the project supervisor on specifics for this project +The assignment is part of a fourth-year minor. The assignments will be discussed with the project supervisor on specifics for this project. This will give the team the ability to direct the project. \subsection{Problem Analysis} CodedFun Games is a small, single-person game company looking to scale up. The owner, who is also a game programmer, graphical artist, and the client, has received government funding, which he wants to invest in a custom-built game engine. The owner has no interest in developing or maintaining a game engine himself, so he has hired a part-time engine programmer. This programmer does not have time to create an entire engine but is willing to maintain or expand an existing engine one day per week. @@ -39,6 +39,9 @@ week 17: eind oplevering \section{Risks} \subsection{Techincal Risks} +Multiplatform: The team works in linux and windows which poses a risk for the development if there is a platform dependencies. +Integration: Users can make a wrong integration causing for delay or risk of losing code. + % todo add technical risks \subsection{Project Management Risks} Scope Expansion: There is a risk of creating a scope that is bigger than the requirements. @@ -47,7 +50,8 @@ may hinder progress. \subsection{Measures} Scope Expansion: By writing detailed requirements and having weekly team meeting to check if the progress is within the scope should be sufficient to decrease the risk. Lack of Team Collaboration: Weekly team meetings will result is collaboration among team members and discussing what each other tasks is will decease this risk. - +Multiplatform: The team can switch any time to a single platform so this risk is metigated. +Integration: By follwing standard and having an integrator which checks every pull request this risk is minimilised. % Documentation Standard is described here \section{Documentation} -- cgit v1.2.3