Documentation Review of Requirements Management MVC
References
Per this Iteration Office Hours Recording, it was recommended that for the sake of iteration, documentation be included as part of the MRs, but that Technical Writing take a final look at things after the fact.
The purpose of this issue is to ensure that Technical Writing has a chance to review all documentation created as part of the Requirements Management MVC Epic.
Related issue(s):
Further Details
Allow Technical Writing to have a chance to perform a final review of all documentation created as part of the Requirements Management MVC.
Feedback Received from Slack Release Announcement
It would be great if the documentation for that (Requirements Management) feature had a specific example rather than lorem ipsum. I'm having some trouble understanding the purpose.
We should bring to the docs some content from the release post description and even the direction page