HI guys, i was wondering whether any of you would be able to give me some advice...

As part of my work experience i have been assigned a new project. Pretty much i have been posted at a marketing agency which uses a massive CRM software.

As part of my requirements gathering, my project manager has told me to analyze the user guide of the CRM system they are using to gain requirements, as the employees are very dependant upon the system. 

I was wondering when performing this whether i should look into alternative comparable software packages and if so what kind of criteria i should use to analyze the strengths of the software.

tPS this is my first requirements gathering using Document analysis so any help would be great

Thanks everyone,

Kind Regards, Navi

I also agree that you'll need to do more than look at the user manual to find the requirements of the current CRM, but it can be a good first start. I would begin to document the features that i could find from the user guide and then meet with the users to document the rest. I would use a context diagram to identify the scope of the current CRM to identify all of the major functions and external systems. If the users have any pain-points or features that aren't present in their current CRM system, then I would document them and create a 'to be' model. Lastly I would prioritize the list with the users and use that list to go shopping for a new CRM. Before you can shop for a vendor package, you need to know what are the important functions the business is looking for.

Reading the documentation is actually  useful step, but like the others have said - it won't be enough.

If you can't access real users you should go to a system administrator or programmer and get them to talk you though the system's main functions.  They may not be usre about what value functions add but you can posibly use your won judgement.

Poentially try to cme up with a "features and benefits" list.

Other places to go include;

• Fault tickets
• Change requests/enhancement requests to the system
• Original requirements specs from when the system weas first introduced

Lastly - you should be able to get the time of someone who knows the system.  Go have lunch with them and discuss it there.  That's part of teh BA' arsenal of tools - getting things done via the unofficial channels.