Slides from my talk at apidays New York 2020 on the open and lean APIOps Cycles method

1. APIOps Cycles
HOW TO DEVELOP BUSINESS AND TECH TOGETHER
MARJUKKA NIINIOJA, OSAANGO
APIOps CyclesTM
https://www.apiopscycles.com/
For lean and business-oriented API
Development
Openly licensed with CC-BY-SA 4.0

2. Marjukka Niinioja​
Founding partner Osaango Oy​, local organizer of apidays Helsinki
(again on Sept 1-2) and APIOps meetups
​Consulted and trained 200+ companies and public sector organizati
ons on platform economy and
API economy business models, service and product strategies and e
nterprise architecture​
​One of the authors of API Economy 101 –
book (2019) combining research with practical experience​
“Mother” of APIOps Cycles method.
Linked https://www.linkedin.com/in/marjukkaniinioja/
@mniinioja​
@osaangoltd​
@apiopscycles​
#apieconomy101​

4. APIOps Cycles helps you to remove the 8
wastes of Lean
APIOps
= DevOps for APIs,
but
APIOps Cycles method
= a specific method combining
APIOps + “BizDevOps” + Product
management + Minimum Viable API
Architecture + Lean

5. @apiopscycles is not just for single API
 It’s also for
 API strategy,
 business model or
 planning for API management
rollout.
 And for knowing which APIs to
buy, steal(!) or borrow

6. It’s all about collaboration
 If your API team looks like this
– APIOps Cycles won't help
you.
 Invite who ever you need to, to
get to the real truth on what
your partner strategy and API
strategy should be, and how
APIs could be used in your
business model.

7. Who do you need then?
 Invite your business, marketing,
different genders, nationalities,
seniors, juniors, customers,
partners and your favorite API
consultant with you.
 Offer them cake, drinks and
@apiopscycles API canvas and
tell them how this
helps them to
achieve their goals.

8. @apiopscycles Use cases - API strategy:
 Take one business unit and one
ecosystem journey customer
segment first.
 Go through API Canvas-phase
and do around of partner and
developer experience reviews
first.

9. Key ActivitiesKey Partners
Costs
Key Resources
Name of the API
Relationships
Channels
API Consumer Segment
Revenue Streams
23
4
5
6
7
8
9
API Value Proposition
1
API Canvas
Water meter
technology
companies
Water services
providers
 …
 …
 Support,
communications, sales
etc..…
Integration support, Data storage and maintenance
Developer community growth and management
API, SDK etc. Development
Other risk reducing costs (see Business Impact)
 Construction planners
 Real-estate owners
 Construction planning
software providers
 Building maintenance and
autom. companies
 Energy companies
 Security of supply bodies
 Water services systems
 XXXX € / month
 Monthly data included in supply fees, 99,5 & 24/7
SLA, day-old data and over 90 days retention with
extra fees
 More quota and more sources = more revenue
 Water
consumption
and quality
data for your
building /
real-estate in
a standard
format
 Integrate with
all the other
utility data
 Water cons. API
Developer
experience
Development
activities
Business model of the API & API
provider
 … Construction planning
software providers
 Data hub providers
 Own developer site
More
potential API
consumers
www.apiopscycles.com

10. @apiopscycles use cases - API
management technology planning:
 Start with API strategy
and then use the NFR
canvases (Business
Impact, Capacity,
Locations of data and
systems.
 Give a thought on the
API design (events or
polling with requests).

11. @apiopscycles use cases - building an
app #APIfirst
 When you build an app, you will
also build or use APIs.
 With mobile or SPA you will
expose those APIs as public
anyway, so plan them well.
 At least parallel to designing a
user interface, start with APIOps
Cycles working the whole method
through to ensure you have
considered API security, developer
experience and the more lucrative
business use cases with API only.

12. The @apiopscycles method is technology
agnostic.
 It contains example design
guide and API audit checklist,
which are more REST API
oriented, but should be
considered for GraphQL,
AsyncAPI and others, too.

13. Just add 3 ingredients to start
 Start from your current business
goals. Be ready to toss your initial
ideas away.
 Start from end-customers, but
then move to the developers
needs who have to meet the
needs of those end-customers
 Get the right people together and
get them trained in the method
and the skills related to the
method.

14. Get more info from
WWW.APIOPSCYCLES.COM
WWW.OSAANGO.ACADEMY
Fill the form and get a
personalized implementation
guide for implementing APIOps
Cycles method for your
organization or your customers
https://osaango.typeform.com/to
/Dhi68XFOLLOW @APIOPSCYCLES AND
@MNIINIOJA IN TWITTER OR IN
LINKEDIN TO GET THE SLIDES
QUICKLY AND PARTICIPATE IN
DISCUSSION