Open method for Lean & Business-oriented API design APIOPs Cycles
summary
The APIOps Cycles method packages Lean practices (including Lean Startup and MVP thinking), prototyping, checklists and canvases like the Business Model Canvas into a stepwise process used with 200+ companies to design business-oriented APIs. It targets developer experience and organizational alignment, prevents throwing whole databases at interfaces, surfaces unexpected constraints (for example a partner requiring server reboots), and intentionally kills unnecessary APIs early. The method and materials are available under Creative Commons.
AI-written summary · about
chapters (10)
- 0:00APIOps Cycles method intro
- 3:36Why APIOps Cycles was created
- 8:20API design limits
- 12:14User-centered API dev
- 14:02Ten reasons for API method
- 17:14Copying API designs risks
- 18:39APIs as products and value
- 20:46Cross-functional collaboration
- 21:27APIOps vs DevOps
- 22:33APIOps resources
related talks
22mAPIOps Cycles, how to develop business & software together
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.
13mFrom Chaos to Clarity: Designing (AI-Ready) APIs with APIOps Cycles
24mFixing API Chaos: A Practical, Open Method to Structure API Work
49mBuilding Software Better: API Lifecycle Management for Developers
28mApidays Virtual Helsinki 20 - Marjukka Niinioja, Osaango