Really large teams of Drupal developers, even larger QA teams, a heavily weighting "overload" of custom code, a whole "ecosystem" of repositories... these are just some of the particularities of an enterprise site building process. A process which, if not ideally structured and on backed up by a "healthy" Drupal development routine, with a few basic rules, is prone to error and to "surprise" events right before launch day. Therefore, let me try and make a sort of "draft" list of 7 best practices to stick to when you're Drupal 8 enterprise site building: