Engineering/Arch Capability

Lancez-Vous. C'est gratuit
ou s'inscrire avec votre adresse e-mail
Engineering/Arch Capability par Mind Map: Engineering/Arch Capability

1. Tech DNA

1.1. People

1.1.1. Pulse Surveys

1.1.2. One-ones

1.1.2.1. Effective feedback

1.1.3. Career path

1.1.4. Quarterly Goals

1.1.4.1. Calibrations across TOT

1.1.4.2. Continous feedback

1.1.5. Training

1.1.5.1. Pluralsight

1.1.6. Pay Calibrations

1.2. Leadership

1.2.1. Emerging leaders

1.2.1.1. Training

1.2.2. Coaching/ Mentoring

1.2.2.1. Formal Mentor Mentee program?

1.2.3. 2ICs

1.2.3.1. Seniors/Leads

1.2.3.2. Planning Team Capacity

1.2.4. Team Health

1.2.4.1. Performance v/s Potential Grid

1.2.4.2. Retros

1.2.4.3. Team Capability

1.2.4.4. Elininate SPF

1.2.5. Delivery Metrics

1.2.5.1. Flow

1.2.5.2. Engineering metrics

1.2.6. Comms

1.3. Branding

1.3.1. Recruitment

1.3.1.1. team scale up

1.3.2. Tech Blog(Hamish)

1.3.3. External Perception

1.3.3.1. Meetups

1.3.4. Technology Parity with Orgs

2. Big/SmallRocks

2.1. Strategic

2.1.1. Tech Debt

2.1.1.1. Risk Register

2.1.2. Enterprise Soln Architecture vision

2.1.3. A/B Testing

2.1.4. Chaos Engineering

2.1.5. Capability

2.1.5.1. Frictioneless Operating Model

2.1.5.1.1. Documentation

2.1.5.1.2. Process

2.1.5.1.3. Architecture intake

2.1.5.1.4. Clear Roles and Responsibilities

2.1.5.2. Platform Strategy

2.2. Tactical

2.2.1. Speed to Market

2.2.1.1. PR Process

2.2.1.1.1. Hotfix PR process

2.2.1.1.2. Feature PR review

2.2.1.2. CI in AU

2.2.1.3. Testing

2.2.1.3.1. Shift Left Testing

2.2.1.3.2. Exploratory

2.2.1.3.3. Automation Coverage

2.2.1.3.4. Login Error Analysis

2.2.1.4. Environment

2.2.1.4.1. Staging - Repurpose UAT

2.2.1.4.2. Ownership Per TOT

2.2.1.4.3. Optimus across all reigons

2.2.1.4.4. Dedicated compliance environment for regulator testing and approvals

2.2.1.5. Deployment without downtime

2.2.1.5.1. Blue Green

2.2.1.5.2. backward compatibility?

2.2.1.5.3. US single app dependencies

2.2.1.5.4. Move Global components to regional?

2.2.1.6. App monitoring / alerts

2.2.1.7. Hotfix Process (context switching )

2.2.1.7.1. Business alignment / approvals

2.2.1.7.2. Ownership to be cleared up

2.2.1.8. Access Issues

2.2.1.8.1. Feature toggle

2.2.1.8.2. remove manual dependencies

2.2.1.9. Planning Revisited (SDLC)

2.2.1.10. End to end release automation

2.2.1.10.1. Release note automation

2.2.1.10.2. Consolidated release note for all jurisdictions

2.2.1.10.3. Automate Release cut off activities

2.2.2. Technology First Org

2.2.2.1. Tech Radar

2.2.2.2. Guilds / COPs

2.2.2.3. Brown Bags

2.2.2.4. Hack Days

2.2.2.4.1. Mini Hack Days

2.2.2.5. All Hands Tech (AU)

2.2.2.6. Delivery Comms maturity

2.2.2.7. Technology Parity with top Wagering

2.2.3. Simplify Process Overload

2.2.3.1. Services Catalog

2.2.3.1.1. Service Boundaries

2.2.3.1.2. Domains / sharing work across TOTs

2.2.3.1.3. Jurisdictions

2.2.3.2. MonoRepo

2.2.3.3. Config Management

2.2.3.4. Sensiblle Defaults

2.2.3.4.1. Arch - Context,Components

2.2.3.4.2. Design Patterns

2.2.3.4.3. DOD

2.2.3.4.4. Documentation

2.2.3.5. App Support maturity

2.2.3.6. Clean-up slack/ceremonies

2.2.3.7. TimeTracker process

2.2.3.8. Refactor

2.2.3.8.1. WebMicro

3. Powering CX

3.1. State Rollouts

3.2. Product Roadmap

3.3. PB as a Platform

3.4. Event Readiness Platform scale

3.4.1. SRC 2022

3.4.1.1. TBS Decoupling

3.4.1.2. Racing Uplift?

3.4.1.3. Settlement

3.4.2. OF Sports

3.4.2.1. Marketless Markets

3.5. Personalisation

3.6. In-Play Betting

3.6.1. Uptime

3.6.2. Depth & Breadth of markets

3.6.3. Product differentiators

3.6.4. Margin

4. Strategic Direction

4.1. Engineering Culture

4.1.1. You build it, you own it

4.1.1.1. Building with an operational mindset

4.1.2. Celebrating Success

4.1.3. Foster Positive Environment

4.1.3.1. Team First

4.1.3.2. Lead by example

4.1.4. Empowered teams

4.1.5. Psychological safety

4.2. Speed to Market

4.2.1. Fail Fast

4.2.2. Faster Feedback

4.3. Simplify Process Overload