Documentation feedback can come from several source. We must make sure to take care of documentation feedback. And if changes are required, we must make sure these changes are actually made to the documentation.
| Name | Responsible | Description |
|---|---|---|
|
Receive and assess documentation feedback |
Services |
The services department can receive feedback on documentation. This can come from several sources. Sources are, for example:
The service department assesses the feedback, and if a documentation change is required, informs the technical writer.
|
|
Do triage of documentation feedback and estimate work |
Technical writer |
The technical writer can receive feedback on documentation from the service department. Feedback on documentation can come from several sources, for example:
The technical writer assesses the feedback.
If a documentation change is required, the technical writer creates a DevOps task with description and estimated time of the required work in number of hours.
The documentation task is added to the appropriate product increment PBI.
|
| Name | Responsible | Description |
|---|---|---|
|
Receive and assess documentation feedback |
Services |
The services department can receive feedback on documentation. This can come from several sources. Sources are, for example:
The service department assesses the feedback, and if a documentation change is required, informs the technical writer.
|
|
Do triage of documentation feedback and estimate work |
Technical writer |
The technical writer can receive feedback on documentation from the service department. Feedback on documentation can come from several sources, for example:
The technical writer assesses the feedback.
If a documentation change is required, the technical writer creates a DevOps task with description and estimated time of the required work in number of hours.
The documentation task is added to the appropriate product increment PBI.
|
| Related to | Notes |
|---|---|
|
Add documentation feedback work to DevOps |
