Implication to Accommodation Product Direction Q4 2017 - 20 Sept 2017
Team,
Our focus for this week is to ensure full traveloka uptime and diminish any instability arising from our current and upcoming releases.
Our goal this week:
1) To support full recovery and robust product uptime of Traveloka products as a whole
2) To ensure that Traveloka product family is able to continue its momentum of releases - and not be a bottleneck for other product teams or introduce excessive risk as whole
3) To identify and derisk all upcoming releases that may potentially break/introduce accelerated usage of any of our systems be it NE or hinv/aprsapi/aprcapi.
Let's support one another and support others in our Traveloka product family.
As good Traveloka citizens, please identify all potential risks with your team for the upcoming releases and, work together to create mitigating steps to ensure we accomplish this together.
What we commit to do:
- Support the change freeze in NE - see NE_Local_Service_Change_Freeze
- Inventorize all upcoming and in development Accommodation changes that impacts NE or changes NE
- Provide robust justification and obtain explicit approval for prioritization of these projects from @nida, @denni and @alfan
- Obtain explicit approval from @evan.yonathan, @prashant.verma, @irfan, and @denni and informing all stakeholders in release-and-hotfix
-
What we can afford to do:
- Postpone upcoming app releases to 2.18 if any of its services needs to be refactored for scalability
- Significantly reduce the scope of development in Q4 2017 for feature teams in exchange for robust and predictable outcomes
- Reassign mission tasks that grows the business that may not require new development or optimization of existing product features
-
What we will do together:
- Identify all potential risks (whether realized or otherwise) that may introduce accelerated usage in memory
- Support and encourage our team members (engineers) to create mitigating steps that derisk any of these operations or allow for easier feature control so as to be able to pull out/suspend if necessary or other solutions as necessary
- Proactively highlight what the team needs to @nida, @denni or @alfan - so we can support you in this
- Budget for necessary development time to pay off technical and design debts in your features so as to enable us to move nimbly forward