Business want Agile IT teams to scale, but often does not give adequate support for the right implementation. In this presentation we will build a business case for agile practices, team structures and principles of team design by drawing parallels from software architecture.

1. Architecture parallels
for scaling Agile
-Abdul Salam @ aconex
1

2. Why the topic?
2

3. Business wants to scale IT

4. Business wants IT to go agile

5. But no adequate support for agile practices

6. Do you believe in Agile?

7. Our mission
Build a compelling business case to support
agile practices

8. Architecture has solved scaling problems

9. Agile & Architecture share striking similarities

10. Why should I listen to You?

11. I’m one among You
I’ve built teams

12. Lets start…
12

13. 13
What is Scaling?
More Users
More Feature Requests
Architecture Teams
Ability of a system to maintain behaviour under high loads

14. Distribution,
Redundancy,
Loose Coupling,
High Cohesion,
Fault Tolerance,
Autonomy
14
Systems that scale share
some common principles

15. Architecture parallels for Agile
Practices
15

16. 16
Distribution is a reality and will continue to be..
More networked
devices,IoT, More Data,
More network traffic, more
data analysis.
Processor is lagging
behind network traffic
growth. So multiple
processors. Array of small
processors are cheaper.
Fast paced business, more
business features, cannot find
enough developers in one
location. More leverage of
timezone differences. Cost.
Architecture Teams

17. 17
Redundancy
Faster Response,
Fault Tolerance
More delivery throughput,
Business Continuity
Architecture Teams

18. 18
Redundancy Continued…
Data/Process Redundancies:
Web Clusters, Hadoop,
Cassandra
Skill Redundancies: Pairing, Pair rotation
Process Redundancies:
Feedback: Pairing, Local Builds,CI Builds
Feedback: Pairing, Standup, Retro, Demo….
Architecture Teams

19. 19
Distribution makes it hard…
Data Consistency across
networked nodes
Alignment On Culture and Practices
Architecture Teams

20. Architecture parallels for
Team Structures and
Principles
20

21. 21
Consistency in Principles,Contracts
Java,
Maven,
Jenkins
Ruby,
Rake,
Go CI
Java,
Gradle,
Team City
Consumer Driven
Contracts,
REST/HTTP
Scrum,
Skype
KANBAN
,
IRC
ScrumBA
N
Hangout
Responding to
business is
topmost
priority,Topic
Channels over
personal
contacts
Autonomy in implementation
Consistency in Principles
Autonomy in practices
Architecture Teams

22. 22
High Cohesion
OrderPayments
Customer
Order Payment
s
Customer
Loose Coupling
Architecture Teams
OrderOrder
OrderOrder
Independent Scalability

23. 23
Fault Tolerance
Graceful Degradation of
Services, Circuit Breakers
Leaner cut of Priority Features,
Empower for Local Decision making
Architecture Teams
Session Serialisation Minimise people dependency

24. Get Agile Right, IT will Scale
24

25. 25
How do I get it to work?

26. Strong Product Management
26
Usabilit
y
Feasibili
ty
Viability
UX Tech
Busines
s
Divergence Convergence

27. 27
The economics of scale

28. 28
Viability and Feasibility of Scale
Commodity General Purpose
Hardware
- Substitutability
- Cost Advantage
- On Demand Provisioning
Learning Generalists(Commoditise
knowledge*)
- Substitutability
- Cost Advantage
- Dynamic team formation*
Architecture(Cloud) Teams

29. 29
and finally

30. 30
Shift in thinking from
Cost per part Accounting to
Throughput Accounting

31. 31
Thank You!

32. 32
https://in.linkedin.com/in/abdul-salam-909b5b32
abdul.prof.connections@gmail.com