...
| Page Properties | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
Background
T-Systems is taking longer than expected and per Elias is quite lost. Since we have a big push from many customers for CBA (specifically mobile) and this is a blocker, I am proposing that we take this on internally.
Relevant data
After speaking with Elias, he agrees that we should build this ourselves (especially given the demographic of those demanding the feature).
According to Elias, we will have to push Multi-Server feature out 1 month to work on CBA for Android. Since CBA for Android is a blocker for many large customers, and multi-server is not, we agree that CBA is higher priority.
Options considered
Option 1: | Option 2: | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description | Wait for T-Systems | Build internally | ||||||||||||
Pros and cons |
|
| ||||||||||||
Estimated cost |
|
|
We can continue building multi-server feature without interruption 
Unknown timeframe on a highly demanded feature