Teams 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

The following are the teams that currently exist in our company.



Accountable for


Central Services

Central Services


Solution Team

A group of customers, Managed Service v1 product group


Solution Team

A group of customers


Solution Team

A group of customers, Managed OpenShift 3 product


Central Services

Marketing, Sales and Customer Success


Product Team

APPUiO Managed product group

Team Requirements

  • 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

  • Members assigned to the Team in LDAP

  • Optionally an amount of Jira dashboards and boards

  • Clarity on how the Team accounts for their Domain.

  • Clarity what Management Topics the Team has to handle and how they do it (outsource, roles, etc.).

How VSHNeers join and change teams

VSHNeers assignments to teams is done using VSHN Improvement Proposals, by 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