Scrum Bangalore 16th Meetup - March 5, 2016 - Replicating Architectural Scaling Patterns in Growing Agile Teams - Abdul Salam - at Prowareness

1. Replicating Architectural
Scaling Patterns in
Growing Agile Teams
-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

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

15. Few parallels from
Architecture
15

16. 16
Distribution
More networked devices,IoT,
More Data, More network
traffic, more data analysis.
Colocated system cannot
handle it. 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
Architecture Teams

19. 19
Problems of Distribution
Data Consistency across
networked nodes
Alignment On Culture and Practices
Architecture Teams

20. 20
Consistency on Contracts
Java,
Maven,
Jenkins
Ruby,
Rake,
Go CI
Java,
Cradle,
Team City
REST/HTTP
Scrum,
Skype
KANBAN
,
IRC
ScrumBA
N
Hangout
Scrum
Slack
Autonomy in implementation
Consistency on Principles
Autonomy in operation
Architecture Teams

21. 21
High Cohesion
Order Payments
Customer
Order Payment
s
Customer
Loose Coupling
Architecture Teams
OrderOrder
OrderOrder

22. 22
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

23. Get Agile Right, IT will Scale
23

24. 24
How do I get it to work?

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

26. 26
The economics

27. 27
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 Teams

28. 28
How do I sell it?

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

30. 30
Thank You!

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