Scoping and requirements gathering
Within a company or project, documentation requests can come from a variety of internal and external sources, including the following:
- A new feature that’s in progress, probably from a product owner
- A new feature that’s already been completed that needs documentation
- A feature gap that’s been identified by you or others
- A content gap that’s been identified by you or others
- A problem that’s been logged by you or others
When you start filling that content need, the first step is to figure out the current definition of done. I say “current” as just because there may be a completion point for the content needed now doesn’t mean it will remain that way forever. Likely, it will not be considered done in the future. However, while there are predictable potential future changes, there are also others that aren't, and finishing the work as completely as possible now...
