KR: Progress from 1 to n real-time features, including at least one owned by another group => 0%
This KR is important because it shows that another team can self-serve to produce a new feature using existing documentation and that scalability requirements to do so have been met.
Measurement can be broadly divided by complexity:
- 33%: Group is groupproduct planning or ~group:certify reusing the existing issue sidebar connection. For example, real-time epic updates on issues.
- 66%: Any group besides groupproject management builds a real-time feature on a relatively low-traffic resource. For example; groupproduct planning implements real-time Epic description updates, requiring a small number of additional WebSocket connections.
- 100%: Another real-time feature on a high-traffic resource; such as MRs or the file tree.
Edited by John Hope