Considering APIs as business products has fundamental implications for the organization, and especially for how software is delivered. This is because, as I've emphasized throughout the chapters of this book, APIs and the teams that deliver them can no longer be considered as IT cost centers; rather, they must be seen as revenue-and-profit-generating organizations that make use of APIs. This has deep consequences for how such teams are organized, measured, and managed.
From a development life cycle standpoint, this means:
- Moving away from a traditional delivery approach, whereby requirements are gathered at the start and it isn't until late in the life cycle that real feedback is collected from ...
