Content for Slider Panel (when blank)

 

 

More Art than Science: Documenting CRM requirements

publication date: Sep 27, 2011
View a Printer Friendly version of this page, allowing you to print the page. Send a summary of this page to someone via email.

When you are creating requirements documentation for CRM and related software, you must talk to and involve the end users and understand their requirements. It’s necessary and both common sense and basic courtesy to do so. It’s surprising how often this isn’t done.

It’s important for user acceptance; to get a system that does what users need it to do; and to make people aware that the way they work is going to change so they start to prepare themselves.

 



Oops, sorry this page is available to members only.

If you're not a member why not join today? Its simple, free and takes less than a minute to join.

To join free, simply click here

If you are already a member, please login.

If you belive you should be able to view this area then please contact us and we will try to rectify this issue as soon as possible.


To gain access to the members only content click here to join. It's simple, free and takes less than a minute to join.

You will be given immediate access to premium content on the site.