RabbinatixDocs
Sign inGet started

Work as a team

Team promises

What one team promises another for a system: uptime, response time, notice before breaking changes, how fast a service is fixed, how fast sign-offs are answered — agreed by both, measured by Rabbinatix.

Open Team promises in the app

What a promise is

A promise is made by the team that owns a system (the provider) to another team that uses it, or to every team, for that system in one environment. Its terms, each optional:

  • Up at least a percentage of the checked time over 30 days;
  • Answers within a number of milliseconds for 95% of checks;
  • days' notice before a breaking change;
  • Down fixed within a number of hours;
  • Sign-off answered within a number of working days: this one is the using team's promise to the provider.

Agreeing

  1. Open Team promises and press Propose a promise.
  2. Pick the system, the environment, the other team (or Every team) and the terms.
  3. Press Propose (or Make the promise for every team). A lead of the other team presses Agree, or Propose a change.

A promise to every team counts as soon as the providing team makes it. Only agreed promises are measured. To change an agreed promise, propose the change: the old terms count until the other team agrees. End… a promise needs a reason, and the other team is told. Either team's lead can set a Review on day: it shows on the team calendar under Deadlines.

How it is measured

Rabbinatix measures with what already happens:

  • health checks of that system and environment count for uptime and response time;
  • sign-off requests count for notice and for how fast they are answered.

Health checks run while someone has the Connections view open, so a promise counts only the time that was checked and says how much: "checked 41% of the time". Below a fifth of the time it says Not enough checks to tell instead of a number that looks better or worse than the truth.

Broken promises

When a term is missed, the promise shows Broken, both teams' leads are told, and a team issue is raised against the providing team: once for each missed notice, fix or answer, and for uptime and answer time at most once a month.