The first tenant of the Agile Manifesto is individuals and interaction. To achieve this simple but powerful state, both the business and development team need to understand a bit about each others worlds. Joel Mason will show us how architects on an Agile team can bridge these two domains and cultures. In the last few years, architectural styles have changed and grown to support the unpredictable nature of the marketplace. With the right mindset and collaboration with business, your company's architecture can become your company's biggest asset for both business goals and development productivity.

1. Evolve or Dissolve
Architecture Brings Business and Development Together
Joel Mason
Systems Architect
@jamason05

2. Change is inevitable.
Evolution however, is optional.
-Tony Robbins

3. It is not
necessary to
change.
Survival is not
mandatory
- W. Edwards Deming

4. What’s dangerous is
not to evolve.
-Jeff Bezos

7. Typical
Grooming/Planning
Session

8. Product Owner Development
Testing

9. Where am I?

10. Do we understand where we are going?
How do we know when we get there?
Are there guideposts along the way?

11. So how does architecture impact
our ability to be agile?

12. Software architecture is those decisions which are
both important and hard to change. ... Said
another way, software architecture is those
decisions which, if made poorly, will make a
project either succeed or fail, in a needlessly
expensive way.
-Martin Fowler

14. Architect
Architecture
Requirements
Ivory Tower

15. Software is more like building a bridge
while both shores are moving.

16. What if we build architectures
that expect change?

17. An evolutionary
architecture supports
incremental, guided change
as a first principle across
multiple dimensions.
-Evolutionary Architecture
incremental guided change
first principle
multiple dimensions

18. An evolutionary
architecture supports
incremental, guided change
as a first principle across
multiple dimensions.
-Evolutionary Architecture
first principle

19. An evolutionary
architecture supports
incremental, guided change
as a first principle across
multiple dimensions.
-Evolutionary Architecture
incremental

21. Business
Users
Technology
X
Architecture

22. An evolutionary
architecture supports
incremental, guided change
as a first principle across
multiple dimensions.
-Evolutionary Architecture
multiple dimensions

23. Actor Pattern Big Ball of Mud
Low Coupling / Low Cohesion High Coupling / High Cohesion

24. Architectural Quantum
An independently deployable
component with high functional
cohesion.
Minimum Quantum
Monolith => Application
Actor Pattern => Actor

25. Domain Driven Design Bounded Context

26. He with the most options wins.
- Survival Axiom

27. Big Ball of Mud
dimensions of evolvability: 0

28. Layered Architecture
dimensions of evolvability: 1

29. Vertical Slice Architecture
dimensions of evolvability: 2

30. Plug-in Architecture
dimensions of evolvability: 1

31. Microservice Architecture
dimensions of evolvability: N

32. An evolutionary
architecture supports
incremental, guided change
as a first principle across
multiple dimensions.
-Evolutionary Architecture
guided change

33. What is an architect?

35. Domain Driven Design Bounded Context

36. Domain Driven Design Bounded Context

38. Fitness Functions

40. The primary role of an architect is to ride the
elevators between the penthouse and engine room,
stopping wherever is needed to support these digital
efforts: automating software manufacturing,
minimizing up-front decision making, and influencing
the organization alongside technology evolution.
-Martin Fowler

42. Resources

43. Thank You!
Joel Mason
@jamason05
joelamason@gmail.com
Summary
• Systems are rarely done, keep
your options open
• Think about dimensions of
change
• Guide change using bounded
contexts and fitness functions
• Be humble, ready to teach and
learn
@Lucas_Systems
lucasware.com/careers/

44. END