Collaboration

For the purpose of better collaboration on dependencies between teams, we suggest some methodologies that have proven to be very effective for teams working together over APIs.

Table of contents

  1. SHOULD Consumers contribute to APIs

SHOULD Consumers contribute to APIs

API Providers are open to contributions of other teams by following the InnerSource culture. Consumers are encouraged to contribute:

  • MUST Bug-Reports
  • SHOULD Feature-Requests
  • MAY Documentation
  • MAY Bugfixes in the API
  • MAY Simple API Features

Teams maintaining an API should actively foster collaboration on their API and should therefore actively maintain a consumer community.

Rational

  • APIs will eventually become “consumer driven” (see also the API Maturity model).
  • The Design of an API is more consumer oriented and therefore provides a better developer usability and more functionality. This leads to lower costs through higher reuse.
  • Better speed of API Consumer teams and much less waiting times of consumers for a feature. Solves the backlog hibernation and thus reduces Cost of Delay.
This site uses Just the Docs, a documentation theme for Jekyll.