Change the pattern - Team strongly coupled with another team - of AI Mentor Studio
266
Views
2
Comments
New
Architecture & Governance 

The idea of the AI Mentor Studio is to show to each teams it's own technical debt.

With these in mind the technical debit of the code pattern "Team strongly coupled with another team" is being set to the wrong team.

At the moment, if we have two teams (Team A and Team B, for example), if the Team B start to use blocks and actions from Team A the Technical debt will appear to Team A, and that's not correct. The code of Team A is perfect, it has no technical debt at all, but by using Team's A blocks and actions, Team B is adding technical debt. The Team B isn't following the best practices, not Team A.

At the moment Team A is unable to fix this debt, once the problematic code does not belong to them, and Team B is unaware of it's own technical debt.
OutSystems should point to Team A with 0% of score, just to inform that their core are being misused, and to Team B it should appear as appear today for the Team A.

I forwarded your idea to OutSystems for some more visibility.

Nice! Thanks.