Or, read, are dependencies killing your organization?
This is what nightmares are made of. Product A, by Team A uses a stored procedure in Product B’s database. Product B is maintained by Team B. Team B updates the stored procedure and tests only their products that depend on the stored procedure. Tests pass. Changes roll out. All hell breaks lose for Product A.
What’s wrong with the process? Teams dependencies need to be managed around APIs with clear SLAs. In a large organization, identifying those dependencies across teams and products and replace them methodically with APIs is a hairy task. The code debt is the size of US Student Debt of 15T. No less scary. But, paying it off may as well make a difference between long time survivability of the the product and your organization.
If there are frictions between your development teams, due to dependencies, this may be one way to resolve that.