APIOps Cycles, how to develop business & software together
summary
Method presents APIOps Cycles as a concrete process used while scaling from a few teams to 30 teams in months and claims APIs require two-times devops (separate interface and backend cycles). It uses API canvases and a set of checklists, design guides and automation recipes to cut the eight wastes of lean, get API-first designs sooner, map nonfunctional requirements and decide build vs buy, and shows a water services case plus industry examples like Twilio to prove faster, repeatable delivery and better cross functional reuse.
AI-written summary · about
chapters (11)
- 0:00APIOps Cycles intro
- 1:48Why APIOps Cycles created
- 3:56Traditional API development problems
- 6:43APIs need DevOps twice
- 8:50APIOps Cycles reduces waste
- 10:13APIOps Cycles for business
- 11:37Collaboration beyond developers
- 13:49Engaging stakeholders in APIOps
- 14:53API design canvases
- 16:38Automating APIOps processes
- 17:48Q&A
related talks
23mOpen method for Lean & Business-oriented API design APIOPs Cycles
24mPractical API Strategy with APIOps Cycles
16mMaster API Product Design with APIOps Cycles Method
19mAvoiding the 8 Wastes of Lean API Development with OpenAPI & APIOps.
49mBuilding Software Better: API Lifecycle Management for Developers
25mAPIOps: automating API operations for speed and quality at scale
54mAPI team characteristics and best practices
54mAPI's a drivers for innovative business models