The document discusses the evolution and challenges of agile integration, emphasizing the importance of self-organizing teams and flexible architectures in achieving agility. It highlights the need for effective governance structures and the role of APIs in facilitating integration within a composable enterprise. Key concepts include managing team flow, overcoming traditional barriers in development processes, and the transition towards a digital-native landscape.

1. CTO and Co-Founder, WSO2
paul@wso2.com
@pzfreo
Paul Fremantle
Enabling Agile Integration Teams

4. http://2011.igem.org/Team:UNIPV-Pavia/Project/Modelling

5. Biology is fundamentally the
study of complex systems

6. Agile is here
- just not very
evenly distributed

7. CONSUMER DEMAND
SUPPLIERS DISAGGREGATE ARCHITECTURE TO MEET DEMAND
1
10
102
103
105
109
MONOLITHIC
BUSINESS APP
ENTERPRISE APPS DEPARTMENTAL
APPS
SAAS APPS PUBLIC / PRIVATE APIS SERVERLESS &
MICROSERVICES
1970s
|
MAINFRAME
1980s
|
IT AWAKENING
1990s
|
INTERNET
2000s
|
MOBILE
2010s
|
IoT/AI
2020+
|
DIGITAL NATIVE

8. Physical
Functional
Linux/OS
Virtualization
Cloud
Containers
K8s, Cloud
Orchestration
ABIs Web Services SOA APIs Endpoints
Cloud Native

9. Niels Bohr “ “An expert is a man who has
made all the mistakes which
can be made, in a narrow
field.

11. Agile - Developer Flow

12. Agile Flow for
Development Teams

13. What Interrupts Team Flow?

14. The wrong organization interrupts flow

15. App Logic
. . .
Scaling HA Resilience Observability
Scaling HA Resilience Observability
HA Resilience Observability
Compute Network Storage
Ops Infrastructure
Centralized
Dev Org
Middleware
& Integration
CoE Teams
Ops
Team
HA Resilience ObservabilityScaling
INTEGRATION
HA Resilience ObservabilityScaling
MESSAGING
HA Resilience ObservabilityScaling
DATA
HA Resilience ObservabilityScaling
SECURITY
App LogicApp Logic
App 1 App 2 App (n)
Fast Waterfall
“Wagile”

17. Complex processes
interrupt flow Step 1 Step 1 Step 1
Step 2 Step 2 Step 2
… … …
Step n Step p Step q
SGMM
SOA
Governance
Planning
Assessment
SOA
Governance
Capabilities
Heat Map
SOA
Governance
Transition
Plan
SOA
Governance
Assets Techniques, Checklist,
Guidance, Examples
Governance Process
Models

18. The wrong
technology stack
interrupts flow

19. The best architectures, requirements, and designs emerge from
self-organizing teams.
The Agile Manifesto
Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant
pace indefinitely.
Deliver working software frequently with a preference to the
shorter timescale.
“
“
“

20. Physical
Functional
Linux/OS
Virtualization
Cloud
Containers
K8s, Cloud
Orchestration
ABIs Web Services SOA APIs Endpoints
O
rganizational
Composable Enterprise

21. The best architectures, requirements, and designs emerge
from self-organizing teams.
The Agile Manifesto
Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant
pace indefinitely.
Deliver working software frequently with a preference to the
shorter timescale.
“
“
“

22. A team which:
● Manages its own work
● Pulls work
● Doesn’t require “command and control”
● Communicates effectively with each other
● Is not afraid to ask questions
● Continuously evolves skills and capabilities
What is a “self-organizing” team?
https://www.scrumalliance.org/community/articles/2013/january/self-organizing-teams-what-and-how

23. Self Organizing Teams
https://www.testingexcellence.com/10-traits-agile-self-organizing-team/

24. Two Pizza Rulehttps://flic.kr/p/X9B7CH

25. n(n-1)
2
Simple maths

27. A self-organising team doesn’t make
every decision...

28. Governance vs
Autonomy

29. 29Governance can interrupt team flow

30. The cell is the basic structural,
functional, and
biological unit of all known
living organisms

32. Cell boundaries
Transmembrane receptors and signalling

33. Why did SOA fail to
live up to its potential?

35. APIs are designed for boundaries
● Authentication required and expected
● Authorization
● Rate limiting / Throttling
● Analytics and Observability
● No assumption that others will use it:
○ Developer-friendly portals
■ SDKs, samples, forums
○ Developer-friendly governance
■ Versioning, Deprecation notification, etc

36. Control Plane

37. Data Plane

38. API-driven integration agile architecture
ESB / Centralised Integration
Legacy systems / Layered Architecture
API Management Global
Control
and
Data
Planes
Cell

39. Self-contained
Deployable as a unit
Independently elastic
Data plane and control plane
Cells Are Building Blocks For The Composable Enterprise

40. Enabling
agile teams

44. 44
“If You Can't Measure It,
You Can't Improve It”
Peter Drucker

45. 45
https://www.tasktop.com/blog/5-best-metrics-youve-never-met/

46. MTTR
46
https://dzone.com/articles/reducing-mttr

47. Flow efficiency
47

48. Boundaries for Agile Integration
● Have a clear global data and control plane
○ An API Management platform provides an effective global control
plane
● Ensure teams offer clear boundaries
○ Versioned APIs managed through the global control plane
● Give teams freedom to evolve within those
boundaries
○ Within a cell they are free to use any approach

49. Cell boundary =
Team boundary

50. Developer first integration
Edit, ShareObserve
BuildDeploy
Debug
And Test
Developer
Flow
IDE integration:
Eclipse, IntelliJ,
VSCode
CI/CD:
Jenkins, Travis,
Codefresh
Test Frameworks:
SOAPUI, TestNG
Code repos:
Github, Gitlab
Binary repos:
Maven, Ballerina
Central, JFrog
Cloud
Orchestration:
Docker,
Kubernetes,
PCF, AWS CF, etc
Observability:
Splunk,
Prometheus,
Jaeger, ELK
Staging:
Blue/Green Deploy
Canary
Continuous Deploy

51. Developer first integration at WSO2
● Ballerina
● Microservices product stack
○ MicroIntegrator
○ MicroGateway
○ MicroBroker
○ MicroStreaming / Siddhi
● Developer tooling that produces immutable
containers

53. Timelapse of Sponge Reaggregation - https://www.youtube.com/watch?v=SvtDMo7fjAc

54. The recoupling of
decoupled components
into new agile teams
Based on teams, with
devops, cloud
infrastructure and intra-cell
comms
Agile inside the cell,
versioned and gatewayed
at the boundary
https://blog.cirm.ca.gov/

55. “Remember that every science is
based upon an abstraction... All
sciences are differentiated by their
abstraction.”
Fulton J. Sheen

56. Everyone is on a journey towards agility
Integration agility needs to catch up with project agility
This means a shift towards enabling integration agile teams
Reaggregating with a cellular architecture and
self-organising teams creates a composable enterprise
Flow metrics allow you to understand cell health

57. THANK YOU
wso2.com