the minimum enterprise viable platform
TRANSCRIPT
Research & InnovationAPI & Platform
Business Strategy & Digital TransformationNew Usages, Connected Business & Mobility
The Minimum Enterprise Viable Platform
William El Kaim – May 28, 2015 – Club Urba EA
Executive Summary
• Ecosystems are dynamic and co-evolving communities of diverse actors who
creates and capture New Value through both Collaboration and Competition
• A “platform” is a powerful type of ecosystem
• Firms could not buy “off the selves” their business platforms, they just do not
exist ! Two main options:
• Build from scratch: follow the blue ocean approach
• Leverage & Extend: by reusing and orchestrating the core business services already
existing, but no more adapted to new usages and demands.
• Introducing the Minimum Enterprise Viable Platform
• Plug-and-play bus. model allowing participants to connect, exchange, & create value.
• Adapted to Enterprise, Resilient & anti-fragile and governed.
• A great opportunity for the rebirth of the Enterprise Architect role
2
A “platform” is
• A technical AND organizational context in which a community can interact to
achieve a specific purpose.
• Typically created and owned by a single business or entity.
• but deliberately designed to attract the active participation of other actors.
• Always at least two-sided.
• Most Platforms start as product (one-sided), then adds a second side (developers,
merchants, crowdsourcing, etc.) when the product gets traction.
• The two sides of the platform should be able to interact through it.
• Designed primarily to:
• Create new markets by enabling connections between previously separated potential
buyers and sellers and reducing drastically barriers of entry
• Focus on the distributed development of new products, services, and solutions (open
innovation).
Source: Deloitte Univ. Press 3
Platform Layers
• Across all platforms, we observe the following 3 layers
• Every platform is a different configuration of this stack
Source: Platform Thinking 4
Platform: Technology Elements
• Platform: The extensible codebase of a software-based system that provides
core functionality shaped by apps that interoperate with it, and the interfaces
through which they interoperate
• App: Add-on software subsystem or service that connect to the platform to
add functionality to it.
• Ecosystem: The collection of the platform and the apps specific or linked to it
Platform A
Platform A API
App
Platform Dependent Services
App App
Ecosystem
Platform B
Platform B API
Platform owner
Complementorsmono or Multi-sided
5
Enterprise Technology Landscape Evolution
Technologies evolution are opening new opportunities for
firms to disrupt themselves and build their own platforms
Technology Darwinism with a Cause
6
Enterprise Business Platform
7
IT core services
Legacy Bus. App
Commodity
services
CRM, social
network, etc.
Product-As-A-ServiceSovereign IT
Enterprise Business Platform could not be bought off-the-shelves
Avoid accidental architecture and build your own!
Create the Minimum Enterprise Viable Platform
MEVP definition
• In product development, the minimum viable product (MVP) is the product
with the highest return on investment versus risk.
• Provide just the core features that allow the product to be deployed, and no more.
• Use iterative process of idea generation, prototyping, presentation, data collection,
analysis and learning. The process is iterated until a desirable product/market fit is
obtained, or until the product is deemed to be non-viable.
• This is my personal vision and definition …
• The Minimum Viable Enterprise Platform is the minimum viable set of core platform
services required by the platform owner and the multi-sided business services that will
make the platform valuable and extendable by each sides.
• The term enterprise refers to the fact that the platform will have to interact and extend
existing enterprise legacy assets in a secure and performant way.
8Copyright © William El Kaim 2015
Build Your Own MEVP!
IT core services
Legacy Bus. App
Commodity
services
CRM, social
network, etc.
Product-As-A-ServiceSovereign IT
Core renaissanceBeyond running the heart of the
business, these assets can form the foundation for growth and new service
development through Platforms
9
Build Your Own MEVP!
IT core services
Legacy Bus. App
Commodity
services
CRM, social
network, etc.
Product-As-A-ServiceSovereign IT
Do not re-invent the WheelLeverage existing “commodity services”
either by integrating them in your platform or by being integrated in their platform.
Think ecosystem and co-creation!
10
Build Your Own MEVP!
Give rooms for others to innovate
Listen to the crowd for open innovation + network effect
11
MEVP
Leverage the Core Business Advantage
MEVP: Enterprise Architect Vision
Source: Club Urba EA 12
MEVP
New Strategy
New Technologies
Business
Architecture
Information
Architecture
Application
Architecture
Technical
Architecture
Lean StartupNew Business Model
Service Design
Hybrid CloudInfrastructure as
Code & Lego
Devops & Elastic Infra.New Databases
Non structured andimmutable data
Authentication &Digital Keys Mgt
API – RESTfullBig Data Analytics &
Intelligence
Minimum Enterprise
Viable Platform
MicroservicesApi
Ephemeral AppsAdaptive UX
External SaaS Services
CRM, Marketing, Ads Appstore Mgt
Agile DevHackaton
Elastic App
13
MEVP: Platform Services
API
App
API
App
API
Product
MicroService Architecture
Core Platform Services: Identity Mgt, API Mgt, Key Mgt, App store Mgt, Integration Mgt, Messaging Mgt, Sync & Storage Mgt, Metrics & Analytics, Billing & Payment
Mgt, Deployment & “ilities”.
Buy or Rent(On Premise
vs. Cloud)
Multi-Sided Business Services: API, Business Process as orchestration, Ready to use documentation and Tools for each stakeholder, etc.
Build(On Premise
vs. Cloud)
Platform owner
Complementorsmono or Multi-sided
14
MEVP
Build Your Own MEVP: 3 Options
Inside ITBuild platform internally
Edge ITReassemble, orchestrate & publish
Cloud ITStart from scratch or mirror IT
Platform is built internallyReuse Enterprise IAM, EAI, ESB, Databases Gateway via API Platforms (3Scale, Apigee, etc.) & segmented network
Buy or Rent Enterprise Mobile Back-end as a Service (MBAaS)Deploy On Premise or in the CloudDelegate Security through existing Enterprise IAMUse MBAaS connectors to build services, to orchestrate them and to expose themProvide MBAaS SDK to developers and let them create apps from services
Build Full Platform in the Cloud, No Sovereign IT accessCopy and Sync Data, and use Virtual Machine or Container with devopsProvide SDK to developers and let them create appsLeverage one Cloud Platform: AWS, Azure, Google, Heroku, etc.
Cost Risk Agility TTM
Cost Risk Agility TTM
Cost Risk Agility TTM
15
Edge IT Example: Enterprise MBaaS Convertigo
Multi-Sided Business Services
Create & orchestratebusiness logic
Multi-Sided Business Services Support Developers via SDKEnable easy mobile app development via templating
16
Core Enterprise Platform Services (CEPS)• Identity Mgt (delegation
to Ent. IAM if needed)• Orchestration• Data management (Disc.
Mode and storage) • API and Service exposure
(SOAP/Rest)• Log generation
(transactions, sequences, access….)
• Transaction count &(re-) billing capability
• Notification (Push) service• High availability and
scalability
MEVP
Source: Convertigo
Conclusion
• Platform are changing the rules of competition!
• The attractiveness of a platform to end-users comes not from the platform itself, but from
what they can do with it.
• Platform ecosystems are composed of externally produced complements
that augment the capabilities of a platform (co-evolution)
• Innovations that differentiate platforms often emerge in the downstream part of the
platform’s value chain, the upstream part being the creation of the platform.
• The fate and survival of a platform then critically hinges on the diversity and vibrancy of
its downstream ecosystem.
• Platform should leveraged best of both worlds: new technologies and
advanced in computing AND existing core business services of a company
• Business should evolve to avoid disruption
• MEVP should help sustain the approach
18
EA and MEVP
• Enterprise Architect should be the man-in-the-middle• Business Innovation. Understand future business needs and create agile paths to
enable them at the right cost without breaking today’s day to day business.
• IT Governance. Leverage existing internal business and technical assets without breaking the current day to day business.
• Craftsmanship. Assess and Test new ways to evolve the legacy, to create new services from scratch (microservice) and to hook business services to the MEVP.
• EA should take the lead to design, support implementations and govern MEVP• MEVP is the new agile business backbone (imagine a company “façade + BPM” on
steroids).
• MEVP requires strong governance of information and data exchanged.
• MEVP requires access to the enterprise back-offices using API.
• MEVP should leverage the enterprise Identity and Access Management already in place.
• MEVP should provide to external developers the freedom to innovate by providing them the right logistic and rules to follow.
19Copyright © William El Kaim 2015
Recommended Books
201520112011 20132012
20
http://www.twitter.com/welkaim
SlideShare
http://www.slideshare.net/welkaim
http://fr.linkedin.com/in/williamelkaim
La Revue Du Digital
http://www.larevuedudigital.com/william-el-kaim/
21