# Relaunch 2020 Q3

## Balanced
|Month|Events|SG|BK|LR|GS|P1|P2|P3|GL|Binarium|CI|
|-----|------|--|--|--|--|--|--|--|--|--------|--|
|||Arch, UX|Renderers, Bundler|Interactions, UE|Maps|App|Editor|Web|User-Flow|Data Access|
||
|**Jan**||UI Rework|Renderers|Convert ArchInteraction|-||||User-Flow|User Web Hosting|RAG CI-CD|
|**Feb**||Image Upload|Competition Conzept|Convert ArchInteraction|Swisstopo||||User-Flow||RAG CI-CD|
|**Mar**||Image Upload|Bundler Rework|Cleanup Conversion|Swisstopo|learn|learn|ifc|User-Flow|Project Relations|RAG CI-CD|
|**Apr**||Create Models/Layers|Bundler Rework|Place Features|Offline-Mode|MapLayers|learn|ifc, conzept LandingPages + new project|
|**May**||Create Models/Layers|Ifc Upload|Place Features|Offline-Mode|Move in LLA, Zoom navigation|Load pins based on distance|ifc, conzept ProjectPlatform|
|**Jun**||Arin Support|*(Modeler)*|Section Placement, Cleanup|Map Polish|Zoom navigation, Visual Quality||Landing Pages, Project Creation||ProjectPlatform|
|**Jul**||Arin Support|*(Modeler)*|Section Placement|Map Polish|Settings, Switch project||Model upload||(ProjectPlatform)|
|Aug:warning:||Mac-Support|*(Modeler)*|||||Model Upload|
|Sept:warning:|22. autumn start||*(Modeler)*
|Oct:warning:|Optimal Launch (?)||*(Modeler)*
|Nov:x:|||*(Modeler)*
|Dec:x:|21. autumn end||*(Modeler)*

The table above is incomplete! The purpose of this diagram is getting a feeling for the amount of work that has to be done.  

These Tasks are unassigned:
 - ConventionMode (Why should I upload my Project?)
 - Research_OpenFromWeb -> OpenCommands --> Web_OpenAppCommands
 - Web_Polish --> WebIntegration
 - LoadPinsBasedOnDistance
 - UX_Polish

|-|Legend|
|-|------|
|:warning:|from experience, this time is required to complete earlier tasks. DO NOT ADD TASKS!|
|:x:|release at this time is probably harmful|

##### Conclusion
The `Balanced` team-composition continues in the same manner as before, barely achieving the goal in time with suboptimal usability and untouched polish. The app will supposedly work and contain the most important, desired features, but it won't feel nice. Also it will feel lacking content, since quick-wins that profit from the strong established code won't even be considered. (Usually those features are what make the user explore and stay in the app).

##### Recommendation
The `Optimal` team-composition should seriously be considered.

In the worst case, we already complete the competition module in autumn (which would be a huge surprise). Even if the team is that efficient, we have lots of issues which have been pending for quite a while. Also the Modeler is almost as ambicious as ArchScape.

In the best case, we can establish an efficient powerhorse which can release the Relaunch in autumn, the Competition-Module in spring 2020 and the Modeler in summer 2021.

Ultimately the team consists of positions that Raumgleiter is missing anyways (Dedicated Architect, UX, Frontend, Backend, Unity-Power). If the projects can financially sustain such a team, it is a good investment. If it cannot, ArchScape will probably be a loss.

##### Worries
 - Having a tight deadline with a completely new team is risky. More so due to unpredictable hiring opportunities.
 - The estimates are very rough. The actual production process can deviate quite a lot.
 - There are likely missing nodes in the milestone graph.
 - The timeline above supposes SG still has time to develop content with 3 more team members.