Project Management

Please login or join to subscribe to this thread

user involment in documentation

linkedin twitter facebook   Information Technology   Strategy  
avatar
Shailesh Wagh Fairfax, Va, United States
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.

why?
Sort By:
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Of course - In such situations, the end user is a major stakeholder so they need to be involved in my humble opinion !
avatar
Anupam India
The end user is a major stakeholder, also the requirement may be for a customized documentation based on specific needs.
avatar
David Fowler Scrum Master| Delta Community Credit Union Atlanta, Ga, United States
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.
avatar
Gina Abudi President| Abudi Consulting LLC Amherst, Nh, United States
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:
ADVERTISEMENTS

"The man who views the world at 50 the same as he did at 20 has wasted 30 years of his life."

- Muhammad Ali

ADVERTISEMENT

Sponsors