[andorov]

I think it is also useful to be aware of the specific terms your team might need and introduce words to those more abstract concepts. This frequently happens with naming specific code patterns or important classes in the code, but can also be for how the team operates in general. A DSL for how your team operates.

[LeonB]

A glossary is a good thing to maintain. We keep one often updated in our wiki (at work)