Tools

Our philosophy about tools - new or current

As for everything we do, structure follows strategy. Our tools have to contribute to solving our day-to-day challenges and not be challenges themselves.

Introducing new tools

  1. Check, if we already have a similar tool in use, or already an account with the tool you'd like to introduce. This can be done with the finance/BizAd people.
  2. If there's a new tool you need for a project, always register a company-owned account. It is not allowed to store company-related data in a personal account.
  3. Make it viewable for every stakeholder of your project, e.g. other team members, people from other Thomann departments.
  4. Make sure the tool is GDPR-compliant. In some cases it might be necessary to have a contract data processing.

Change Blog

We use an internal blog to communicate our most recent releases, engineering updates, and strategy information. It's available for team members and everybody in the headquarters to stay up to date with what we're doing. We recommend our team members to subscribe to it by email.

Kenjo

Kenjo is our people & culture tool. It's used for all people-related tasks:

  • requesting vacation
  • calling in sick
  • setting and tracking unit/community/team/personal goals
  • download paychecks
  • etc.

Jira

Jira is the place to collect tasks, projects, visions, bugs and user problems. Every member of thomann.io has access to check what we're working on and which steps we will take to reach our goals. It's also where you find the company backlog.

Jira must be used as a single source of truth for tickets and therefore for all work in progress and backlogs.

Product Backlog

The product backlog contains all tasks for our product teams on a higher level. If it's not daily business the teams get their tasks from this backlog keeping the balance between internal stakeholder requests and solving customer problems. You can find it under the name "epic flow" and use the quick filters to distinguish between stakeholder projects, teams and more.

All our backlogs and boards are prioritized based on value for our users, segment size of users, predicted effect on our northstar metric and effort estimation.

The product lead is responsible for gathering the backlog items, grooming them and setting a priority.

Team Boards and Backlogs

Each team has their own board and backlog. Just search for the team's name in the board section and you'll find it. Depending on the team's way of work it's either a scrum or a kanban board, some teams also have both.

The team product owners are responsible for gathering the backlog items from the product backlog, refining them with the team and setting a priority.

Projects

tba

Workflow

tba