Project Management Central

Please login or join to subscribe to this thread

Topics: IT Project Management, Strategy
user involment in documentation
It is often argued that in building User documentation, the User needs to participate in the development of the documentation along with developer because the User has a better operational feel for the use of the software once it is delivered.

Sort By:

Of course - In such situations, the end user is a major stakeholder so they need to be involved in my humble opinion !

The end user is a major stakeholder, also the requirement may be for a customized documentation based on specific needs.

I vote for user involvement; sometimes there is user context that needs to be considered when drafting the documentation. As a PM, I want that input to ensure that the docs are something that can be used in training and not just another binder to sit on a shelf.

Getting them involved enables for keeping them engaged. Certainly the end user may have contributions of value based on their own expertise, knowledge, etc.

Please login or join to reply

Content ID:

"Nothing so needs reforming as other people's habits."

- Mark Twain