Roger,
What an exciting BA assignment. It looks like the business has already decided that they'll implement ARIBA, which is a good spend management (procure-to-pay) piece of sofware. Here are some pointers.
Prepare
1. Check out Ariba on the net www.ariba.com (its an excellent site full of great material, white papers etc)
2. Think of a retail store raising requisitions- what do you think are their processes?
3. Think of head-office (if the organization has centralised purchasing) - what do you think are their processes?
4. Find out from your PM what the requirement gathering standards are in your org. Familiarise yourself with that; if not create your own or check the internet and find a template.
5. Also ask your PM to provide you with the project plan, and get a copy of the ARIBA implementation methodology. Most large software vendors have a methodology that they follow to install their software. The vendor might even have a standard way in which they record and store requirements. if so, could you get a copy. It will be very helpful and you'll avoid having to rework your requirements.
First 2 interviews
5. Armed with this retail spend management/procure-to-pay knowledge and the right templates (Ariba's or yours) arrange an interview with 2 stakeholders . Tell them what you are after a day or two in advance and set your time limit to 20 minutes for the initial interview.
- Stakeholder 1 (retail store manager) - Ask what they do now (getting an as-is view) with regards to requisitions, approvals, returns, inter-shop exchanges, delivery, invoicing, reporting and budgets etc. Then ask him/her to describe the key processes (limit to 3)
- Stakeholder 2 (corporate purchasing) - Ask what they do now (also getting an as-is view). Find out about suppliers, quotations, prefered suppliers/vendors, order-cycles, etc. Then ask him/her to describe the key processes (limit to 3-4)
- As they explain things, ask for copies of material (eg. paper requisitions or screen dumps)
- for both, ask what is their main problem and what solutions they envisage
- Tell them you'll be back to validate the requirements
6. Return to your desk, with your working papers. Writeup your findings and pass them by your PM. Discuss resources and timings with the PM, and set some realistic expectations. Be carefull not to be swayed to ignore the as-is processes, as later when the new system is implemented, you'll need all the as-is information for data conversion etc. And, more importantly, you'll have to validate the "as-is" to develop the "to be" processes, as it will be required to indentify the gaps and flag functionality that is not provided by ARIBA. Rest assured there will be gaps!
The above is not complete .. its just an approach, that is not too time consuming; but it gives you an early heads-up
warm regards,
K