Can anyone give me some insight on some ways to get business requirements for a RFP. Many functional areas have a stake in the end product, so I would like to get as much direction as possible. My only concern is we may get too much making it impossible to please everyone. Saving Changes...
Sort By:
Michael WoodProject Manager / Business Analyst / Business Process Improvement Guru| Independent ContractorGig Harbor, Wa, United States
Hello Todd. The best advice I can offer is to start with a value-gap analysis and let that drive you to the business processes that need to be improved to close the gap that stakeholders are experiencing. Then organize knowledge workers into cross functional process teams and have them drive the requirments from there. Here is a file that might help. Also, would be happy to send you, with my compliments, my book on Process Improvement. Saving Changes...
Senior Advisor to the CEO| PMISterling, Va, United States
Todd,
If you search gantthead for "RFP", (using the box to your right) you'll get a couple of sample templates that might help. The gantthead package selection process might also be of interest.
Todd, I have a few comments: (1) You have several templates and deliverables available to you provided you are a premium member. In case you are not, here are a few pointers: (1) Do you have a particular group in charge of the project (e.g. eCommerce group). This group should tackle issues like scope. Make sure you have identified a management influencer in this group (someone who makes the final decision). (2) In general try and limit the # of business units. Yes, everyone wants in but first you have to be successful with one or two. Pick departments and/or business units that will deliver the most for each $ spent. NOW REMEMBER...depending on the business problem, technology, and time to market priorities this may change. (3) Limit the number of people representing each department. Select a max of two "ANGEL" users from each department. Ideally one is recommended. This is not really the end user but like a chief business analyst. (4) Find functionality common to all departments. This process will also help you find requirements unique to each functional area. (5) Then determine if the unique requirements are critical to execute core business problems. In general I would go about ranking the requirements on three things Business benefit, technical complexity & organizational readiness. Hope this helps! I can be reached @ [email protected]. Saving Changes...
Matthew YurksaitisOwner/CEO| YFI Enterprises LLCGoldsboro, Nc, United States
Todd,
I agree with Michael Wood. A good starting point is a gap analysis. What are you looking for regarding the POS? an upgrade, new install? either way start with Gap Analysis, you should then look at some of the Requirements Gathering and Management info on this site (including templates) to help you get a handle on pulling the requirements together, prioritizing and managing them.
Once you have the baseline requirements; which you will need to get your key stakeholders to sign off on, then you can start getting down to the business of putting together the RFP.
Sequence and order is important in an RFP process, because if you don't have the info needed to draft a good RFP then you will get the same level quality of responses from vendors.
Having worked on RFP's for many initiatives you will want the RFP to be solid and communicate your needs clearly and well, otherwise the results can be drawn out and painful. Saving Changes...
Matthew YurksaitisOwner/CEO| YFI Enterprises LLCGoldsboro, Nc, United States
Just a quick follow-up to my original post. As it is hard to tell where you are in your overall project I have attached a 1 page basic RFP activity / task outline. These tasks / activites are common to all business sectors and can be tailored to your specific business / project.
Hopefully this is helpfull.
If you have any questions or need more info I can be reached at [email protected] Saving Changes...
PMI Team Member
