Should developer documentation be included in the Definition of Done?

There are a number of things that tend to not be included in requirements that really should be there. The two immediate ones that come to mind are:

* Documentation (business and developer)

* Whatever mechanism you’re going to use to measure success of that feature

I’ve only rarely seen documentation get created outside of when the work itself is happening (and only when something goes very wrong and requires investigation). Similarly if you’re not measuring your feature, it’s very easy to drop months / years of time into it when you might have discovered pretty quickly it’s not something your users want or use.

if requirements are the definition of a features request

Yes