Technical Release Manager in Open Bet

9 вересня 2024

Technical Release Manager

Львів

OpenBet is sport .

OpenBet’s mission is to power growth and player engagement through a global betting ecosystem that delivers at scale, at speed, at every great sports event. Our 1000 talented colleagues are the market’s top team. We achieve billions of bets in a season; 60,000+ per second (more transactions than Amazon on Prime Day); 100% uptime (zero Superbowl crashes!) and we’re built on 25 years of imaginative technology that is iterated daily.

We offer the speed, dynamism and growth opportunities of a start-up, underpinned by the stability and strength of a global employer.
We are hiring only in Lviv so you could meet your team in our office.

Responsibilities

• Manage end-to-end Release lifecycle and process for the Trading System and Risk System products.
• In collaboration with Engineering and Product define the Release scope for Major, Minor and Hotfixes releases.
• Define the release schedule, identify and communicate any breaking changes introduced to 3rd parties integrated into the platform to plan changes in advance.
• Be aware and coordinate the deployments to onboard new customers with the Open Services and SportCast integration teams. Customer onboardings are done without version upgrades and most of the steps in the release flow do not apply.
• Cater for the follow up of JIRA administrations for the tickets. Guide and instruct product teams on the steps they have to do or missed on the tickets they delivered. In details enforce that:
  
  • Ensure tickets included in release have the proper tags
  • Ensure tickets have appropriate release notes
  • Push tickets back to teams for updates
  • Create and maintain JIRA versions (as per process only those released on MTS PROD and OPAP envs)
  • Update tickets in JIRA with the released version (bulk job)
• Define the initial version cut — ideally do the first cut him/her/it/self to trigger the new version release lifecycle start.
• Create the release notes for all internal and external stakeholders after validating of the release notes in each ticket to be properly set.
• Compile different list of release notes for internal and external stakeholders filtering out the irrelevant tickets and setting them on the proper template like:
  
  • Compile the full release notes for the Product Team and Trade leadership
  • Compile the release notes for our Trading Team
  • Compile the release notes for major customers like OPAP that have great interest in each release filtering out tickets and work not related with them
  • Compile the release notes for the OpenBet customers (like NLO, Sazka, BCLC, Betfred etc) including tickets that are relevant to them
  • Compile the release notes for IMGA customers highlighting only the changes in our official feed that affect them
  • Compile the release notes for SportCast customers highlighting only the changes in our SC premium feed that affect them
• From the release notes, collect required deployment steps and dependencies:
  
  • Update runbook with any manual steps and dependencies
  • Ensure all PRs for configurations are executed — ideally raise the PRs him/her/it/self
• Follow up the regression testing phase, defect fixes and backports to the release and update release notes accordingly.
• Green light the release as production ready and define the go live schedule after alignment with the main shareholders (POs, Trade Engineering SLT, Trading Team, GPMO).
• Raise the provide Change Management tickets providing all necessary information to the Change Managing team for the production approval.
• Communicate the release date to all stakeholders handling out the appropriate final release notes to them, including but not limited to:
  
  • Product teams for on call support arrangements
  • Traders/Support teams for awareness
  • Customers through CSMs or PMs for awareness
• Manage the releases execution:
  
  • Stage deployment checking deployment steps accuracy, expected downtime or failed/missing steps to rehearse the production deployment.
  • Production deployment and smoke testing pass.
  • Notify stakeholders for the release completion
• During the lifecycle of the release on UAT/Stage assist in communications with customers on issues reported from their side.

More details about the TS/RS releases:

The OpenTrade product follows a 4 sprint PI planning after which a series of features are included. The output of the PI defines the next major release that will be rolled out to production environments. Depending on the business’s need a release cut can be taken a little earlier or later than the end of the last sprint due to some crucial features not being available and business demands.

Nevertheless, a major release that is cut approximately every two months. Between these two month period we cut another minor release that contains either crucial missing features or group lower priority incidents or non-critical changes that affect platform performance and stability.

Based on the above there is a release scheduled on every month containing a considerable number of tickets. However due to multitenant nature of the platform there are frequent ad hoc micro releases containing P1/P2 hotfixes that need to deployed as soon as possible to avoid problems that could lead to revenue loss. There have been cases where we had done 7 deployments in a single week; on average 1.4 micro deployment per week is done.

The Global Risk and Global Tickers products have a slower release cycle that is on the PI cadence. Usually, urgent deployments are required only in the case a RS sportsbook is upgraded and the security keys to connect to AF are changed and need to be updated.