Collaborating across teams

A developer on a Clean Core programme has standing interfaces to at least four other groups, and naming them up front prevents most friction. Functional consultants own the business processes you must not silently change — you need them to confirm a remediation is behaviour-preserving, or to own the communication when it is not. Basis/DevOps own the transport landscape, the central ATC system, and the CI/CD gate (module 8's topology) — they decide when and how your changes move. Security owns the roles and authorization objects your DCL ties into (the capstone's PFCG-linked role). And where no released API exists, you escalate to SAP through the channel that requests an extension point or a new released object.

The practical mechanism is a light RACI plus explicit handoffs: who is Responsible for a remediation, who Accountable signs it off, who must be Consulted (functional, security), and who is merely Informed (the business owner of a changed screen). The single most useful artefact is a shared definition of 'done' that reads: ATC-clean against the team's union variant, behaviour confirmed by the functional owner, and transport sequenced with Basis.

Collaboration also means not surprising people. The capstone's communication plan and module B1's governance ownership exist precisely so a behavioural change reaches the affected business team before it ships, and so an exemption has a named approver rather than being a quiet developer decision.

Source notes: clean-core-curriculum (delivery synthesis)