Teams

Product teams

  • customer-centric to the users of our web shop and app
  • data- & metrics-driven
  • focus on goals, e.g. improving search or checkout

Product teams combine roles from engineering, product, uiux, and agile to own parts of our web shop and app. They work together with service teams to succeed in their projects.

Service teams

  • engineers and other internal roles as customers
  • improve development experience
  • support product teams in cross-functionality

Service teams usually have their competency in one unit. Examples are our development experience team, operations, data or people & culture. They support our product teams in working end-to-end by providing a specific service, e.g. infrastructure or data analysis. They might also support other departments from Thomann.

Important note: When service teams grow, we'll add their roles to product teams where it makes sense. This enables more autonomous work within the product teams.

Switching teams

Should a team member not feel comfortable (like really uncomfortable) with their team, there's an option to switch teams. The highest priority here is to look for direct communication. There are some requirements for finding/forming a new team:

  1. Functioning teams must endure
  2. Teams must be able to develop features for their focus topic
  3. Teams should consist of people from multiple locations
  4. A new team constellation shall improve our product development

Making teams visible

Make sure your team has a blog post on thomann.io. This will help you introduce the team to your applicants. Important: You own the post. If your team changes, you must change the post as well.

List of teams

Team BK

Topic: taking care of everything after a customer has decided for a product in our web shop.

Team scharf team

Topic: taking care of everything that a customer needs to decide for a product in our web shop.

Team APPic

Topic: taking care of the Thomann mobile app and the API it uses.

Team Toolster

Topic: taking care of content management systems and tooling structure, i.e. tools that are needed by other departments to bring our web shop to life.

Team Operations

Topic: taking care of the infrastructure that runs the Thomann universe.

Team IT Support

Topic: internal (client) IT support, takes care about all client hardware, software and licences, helps you with your device problems. Click the headline to find more information and processes on the related Confluence page.

Team Data

Topic: taking care of our data warehouse, business intelligence, and figuring out what data helps the most in which team or department.

Team Flavortown

Topic: taking care of building a state-of-the-art development experience in the depths of our web shop backend and services.

Team Quality Engineering

Topic: building a test framework to ensure constant improvements in quality for our software.

Architects

Topic: making sure, there's somebody who understands how everything works together. Taking care of simplifying exactly this.