This document discusses dealing with dependencies between teams when developing software. It acknowledges that fixed release schedules and monolithic codebases can create issues. Some potential solutions proposed include using contracts and mocks between teams, restructuring code using domain-driven design principles, and creating lean shared libraries to reduce duplication while allowing independence. The document advocates for moderate approaches between extremes rather than ignoring problems with dependencies.

1. Dealing
with Team Dependencies
Diego Pacheco

2. @diego_pacheco
❏ Cat's Father
❏ Head of Software Architecture
❏ Agile Coach
❏ SOA/Microservices Expert
❏ DevOps Practitioner
❏ Speaker
❏ Author
diegopacheco
http://diego-pacheco.blogspot.com.br/
About me...
https://diegopacheco.github.io/

3. Accepting Conway’s Law

4. Release Calendar
/ Release Trains
(fixed 2 in 2 weeks
release)
ARE
EVIL !!!

5. Do nothing and Keep ignoring the problem.

6. Possible Solutions?

7. The Myth of Full Stack Engineer

8. Extremes create issues
Monolith Distributed
Monolith

9. Real Solutions

11. Contracts and Mocks

12. Re-Structure and DDD

14. Lean Shared Libs
Duplication is fine

15. Self-Service Platforms

16. Dealing
with Team Dependencies
Diego Pacheco