Infobip Engineering Handbook
Start HereJoin Infobip EngineeringBack to Infobip.com
  • Start Here
    • Infobip At A Glance
    • What We Believe
    • Infobip Engineering Timeline
  • Become A Better Engineer
    • Are You Bored At Work?
    • Steep Learning Curve
    • Freedom To Choose Your (Engineering) Hammer
  • Tech Stack & Architecture
    • The Scale of Our Systems
    • Platform Architecture
    • Observability For Quality
  • How We Code & Deploy
    • Development Flow
    • Testing (And The Freedom To Choose Your Tests)
    • Troubleshooting
    • Incident Management
    • Deployments and Disasters RPG
    • Engineering Enablers
    • A-Team
    • Collaboration Tools
  • Engineering Culture
    • Engineering Principles - In Practice
    • How Growth Impacts Infobip's Values
    • Culture of Approachability
    • Paid Interventions
    • How We Improve Our Culture
    • Employee Feedback Process
  • Key Processes
    • LeSS
    • OKRs
    • One Backlog
  • Self-Managed Teams
    • You Build It, You Own It
    • Examples of Infobip Teams
  • Community
    • Student and Youth Programs
    • Engineering Insider
    • Dev Days Conference
    • Meetups
    • Writing for Engineers
    • Publishing your ideas
    • ShiftMag
    • Hack Days
    • Startup Tribe
    • Infobip Shift Conference
  • Career Development
    • Career Development
    • Switching Positions
  • Benefits
    • Benefits Overview
    • ESOP & Bonuses
    • Engineering Education Budget
    • Learning & Knowledge Sharing
    • Attending Conferences (And Speaking At Them)
    • Good Hardware
    • Vacation & Well-being
  • Hiring & Onboarding
    • Hiring Process - Step by Step
    • Your Onboarding Plan
    • Engineering Onboarding Program
    • Referral Program
  • A Day In The Life - At Infobip
  • An Engineer's Log: No Such Thing as a Typical Day
  • 😊Join Infobip Engineering
  • Impressum
Powered by GitBook
On this page
  1. Self-Managed Teams

You Build It, You Own It

PreviousSelf-Managed TeamsNextExamples of Infobip Teams

Last updated 1 year ago

Infobip uses a huge number of data centers, VMs, services etc worldwide, which have to work properly, quickly and reliabliy to deliver the requested service to our clients. Each of these components has a dedicated team which knows its hardware, data storage, VMs, services etc. best, depending on the area that it is covering.

In order to make your work as part of such a team easier, we give each team the freedom to decide and define their way of work through Working agreement, Definition of Done etc., while aligning it with aligned with Infobip principles. The way teams work is different among teamsm and it is not rare that small experiments are conducted with the goal to further improve the work.

Here are some examples on the decisions each team can make:

  • How they will organize on calls (daily, weekly, ...)

  • Will they use Pull request review and/or pair/mob programming?

  • Will they use Scrum or Kanban?

  • When is the feature ready for production, i.e. when can the task be moved to done?

  • How will they use their education time?

  • How will they exchange knowledge and experience?

  • How will they organize meetings? (e.g. "Have an agenda, define outcomes", "Be on time, end on time")?

Teams are also free to choose the tools, technologies, equipment, services etc. which they will use to create their products. Sometimes, this level of freedom can seem intimidating because there is just to many options to choose from, but that's what colleagues willing to help, all 800+ of them, are here for.

You Build It, You Own It

With great freedom, comes great responsibility, meaning that a team isn't only responsible for design and development but also for production. The main working principle is "You build it, you own it.". That is why teams have the responsibility to take care of them and have to ask themselves the same set of questions for each component they are responsible for:

  • Does it work correctly?

  • Does it work fast (enough)?

  • Is it reliable?

  • Is data security ensured?

  • Does it require upgrades?

  • Does it require new funcionality?

The team is responsible for design, development, testing, security, release, configuration, deployment, monitoring, alerting, and troubleshooting. There is no handover to some "QA" team, "Security team," "Operations" team, etc. Many tools, processes, and other teams in Infobip help each team perform all of these responsibilities.