Teams (or circles) are self-governing and semi-autonomous groups of equivalent people who collaborate to account for a Domain.

Each team organizes itself and has its own methodology and rhythms, usually following agile principles. Most of the teams follow a Kanban approach to project/task management (operational backlog) and some kind of governance backlog to track continuous improvement and changes on how they work. They adapt to the requirements of their domain they’re accountable for in real time and communicate in the team every day about the current events going on.

Current Teams

We currently have 4 types of teams
  • Tech Teams are the old format of teams organized more around a group of technology and not around customers or products. The change of this type of teams into Product Teams and Solutions Teams is ongoing.

  • Product Development Teams (in short Product Teams) are accountable for a group of products.

  • Customer Solutions Teams (in short Solution Teams) are accountable for a group of customers.

  • Central Services Teams are accountable for different domains the company and other teams need to be successful.

The following are the teams that currently exist in our company



Accountable for


Central Services



Solution Team

A group of customers


Tech Team

Customers shared with Sirius, mainly VSHN Managed Service v1 based


Solution Team

A group of customers


Tech Team

Customers shared with Polaris, mainly OpenShift3 Platform


Central Services

Marketing, Sales and Customer Success


Product Team

VSHN Syn Support Platform product group

There are also Special Circles which don’t follow the concept of Teams or Delegate Circles.

Team Accountability

Accountability means that teams can be autonomous in what they do and how they do it as long as they take responsibility for their domain at VSHN (for example their customers or products) under the defined constraints and align their efforts with the higher level company or product goals.

Teams make their work transparent to all VSHNeers and participate in decision making through Delegate Circles for topics that go beyond their team.

How to create a Team

Teams are created through VSHN Improvement Proposals and the initial setup is coordinated by Organizational Development.

The minimum a team needs
  • Star name from this list

  • Two or more team members

  • Updated handbook documentation, mainly this

  • Listed on Teams at VSHN

  • Wiki team space

  • Chat channel

  • Listed in Jira drop-down field for teams

  • Members assigned to the team in Odoo

  • Optionally an amount of Jira dashboards and boards

How VSHNeers join teams

VSHNeers assignments to teams is done using VSHN Improvement Proposals, either by creating a new one (new team) or amending the current agreement for an existing team.

If a VSHNeer changes from one team to another, the VIPs of both teams have to be amended and go through decision making. This way we can make sure (in a written way) that both teams are okay with the change.
Steps to do the actual change
  • Update Teams at VSHN

  • Update team membership in Odoo

  • Update team membership in LDAP