Minutes of Meeting Sync 2017-01-30
- Dooms day, worst: Mid Q3 2017
- Mongostrack: 26 Aug 2017
- Mongodwh: 29 Oct 2018
- Mongosdim: 29 Dec 2018
- Notes:
- Use Cases Gathering OK (except marketing eng)
- All listed use cases has owner
- All use cases has importance, except some of marketing eng use cases (target: Wed, 1 Feb '17)
- Stats (TBC):
- 35 of 93 use cases is no longer being used, will check whether there's any data that we could drop
- 11 use cases don't need data eng involvement (domain eng migrate by themselves)
- Insight per Team
- CX has no use case to migrate ( User's customer context might fall into CX though, depend on disucssion between CX & User. Now it is User's by default )
- Backend Infra has no use case to migrate
- Enterprise has 3 use case to migrate, all of them don't need Data Eng
- User has only 1 use case, Customer Context ( related to use case mentioned above )
- Flight has only 2 use case, only 1 need Data Eng involvement ( booking throttling, and it's not really urgent )
- Platform has only 1 use case, and it might fall into Data Engineering / Content Team ( used for feature control & cms handling, need to discuss with content team )
- Payment has 19 use case, most of them related to Fraud detection, sending coupon, and coupon eligibility check ( so far, data eng's biggest stakeholder )
- Hotel and Pricing has 5 use cases to migrate, 1 use case doesn't need data eng
- Web infra has 1 use case related to IP service
- Marketing ???
- Notes:
- Update from Analytics and Marketing, Full Migration 14 Feb still on track
- What's Next?
- Feb 2017
- Data Eng will categorize use cases
- Data Eng will do design based on each category
- Data Eng will choose pilot stakeholder (Domain PM + Eng) based on importance and data growth, and work with pilot stakeholder to deliver successful proof of concept
- Data Eng will stop and drop use cases that is no longer being used.
- March 2017 - Q2 2017
- Domain Eng will migrate each of their use cases