Legacy code can be brittle and lack automated regression tests. When one item is fixed, the risk of breaking other pieces of code is high. To mitigate this risk, do the following: Rotate a developer from the core engineering team to the SE team to help transfer technical knowledge to other team members. Ask the core engineering team to hold brown-bag learning sessions to help transfer knowledge. Practice the test-driven development style for fixing bugs (described earlier), building up unit tests over time, which helps minimize the risk as more tests are added. Allocate the time of a more senior member of the core engineering team to participate in code reviews for the more risky fixes done by the SE team.