Microservice is a buzzword, Agile is a buzzword, DevOps is a buzzword, Java-based itself means so many things… We can continue this way - ad infinitum. What we all really want to see is the real practice! What’s important is how we actually implement a microservice architecture, which techniques and tools we use, how we can structure our teams and our work process. We will show you exactly these thing during this talk! In this talk you will see real examples and hear real stories of the work life. We will see the way we work in agile manner, utilizing principles and practices, and how we build and scale our solutions. It is very interesting to see how the microservice architecture reflects the Agility and how our Agile way of working is changing the microservices. For sure there are pros and cons, success and failure stories, good and bad results - we will tell the real story.

1. Conway's Law in Practice:
Agile Teams & Microservices
BOGOI BOGDANOV
AGILE COACH
BOSNIA AGILE DAY 2018
SARAJEVO, OCTOBER 20TH

2. About me:
• Coached more than 10 teams
• Speaker
• Trainer
• Became a father recently
Contact me:
• LinkedIn: www.linkedin.com/in/bogoi-bogdanov
• Email: bogoi.bogdanov@gmail.com
• Website: www.agilepool.com

3. We are always in a hurry!

4. Bring Bread!

6. Back to the Software world

7. SPEED

8. Software Architecture
Organizational
Structure

9. Monolith Microservice
VS

10. The stories of
three companies

11. 1st Company

12. Organizational Structure
Backend
Team
Testing
Team
Support
Team
Business
Analysis
Team
Integration
Team
Frontend
Team
DB
Team
UI/UX
Team

13. Monolith Architecture

14. We will become Agile

15. Form Agile Teams

16. But…

17. Hard releases

18. 2nd Company

19. Organizational Structure
Development
Team
Testing
Team
Support
Team
Business
Analysis
Team
DevOps
Team
Deploy

20. We will do
Microservices!

21. Microservices Architecture

22. One big release

23. Do the two stories have
something in common?

24. Conway’s Law
“Any organization that designs a system
will produce a design whose structure is a
copy of the organization's communication
structure.”
M. Conway

25. 3rd Company

26. Microservices
architecture
Small cross-functional
teams...
...organized around
capabilities
Flat organizational
structure

27. How small is an
Agile team?

28. 65 Ćevapis
Team
+
6-8 liters of
beer

29. • Self-organized
• Independent
• You build it, you own it policy
• Continuously improving

30. Unleashed velocity

31. Frequent small releases

32. How to handle this?

33. Organized around business
domains

34. Domain 1 Domain 2 Domain 3 Domain 4 Domain 5

35. The side effect

36. I DON’T KNOW WHO YOU ARE
BUT I DON’T CARE WHAT
YOU’RE DOING

37. • Communities of Practice
• Hackathons
• Scrum of Scrum meetings
• Open Space
• Various trainings &
workshops

38. Wrap up

39. Software Architecture
Organizational
Structure

41. Thank you!