[mahomedalid]

I interpret that as:

Pairing - Pair programming, which if one of the developers has experience with the product will solve questions that you otherwise will solve with docs.

Comprehensive User Stories - User story like in Agile/Scrum, where it has an acceptance criteria, goals, description, etc. and can be used to track back documentation of features.

Tests - User test cases, which can be a replacement of the documentation of how to use the product or the intent of the features.