Software Evaluation Part 2 – Best Practices


Here are our recommendations on a few best practices to keep in mind as you complete a Software Evaluation:

Complete an inclusive Requirement Gathering exercise

  • Provides a complete list of desired func tionality
  • Becomes the basis for scoring model
  • Differen tiates software op tions
  • Identi fies func tionality gaps in evaluated systems

 

Create your Request for Proposal

  • Include Functi onal, Interface, Repor ting, implementati on and future support requirements
  • Identi fy all vendors who could be a fit and invite them to par ticipate
  • Evaluate interested parti es and then send the RFP only to vendors who are likely to meet your needs
  • Think about how you will use the proposal after the assessment– gap assessment, scoring model, contract nego tia on
  • Evaluate the results of all vendor responses and create an “apples to apples” comparison

 

Evaluate the Options

  • Design your RFP scoring model to meet your needs (make sure it’s apples to apples!)
  • Conduct vendor demonstrati ons so you and your users can see the software first hand and rate it
  • Conduct Reference Checks– see how peer companies use the same package and what their vendor experience has been
  • Calculate the Total Cost of Ownership (TCO), including software, implementa tion and maintenance

 

Create a formal recommendation based on:

  • Fit across functi onal needs
  • Demo results
  • Reference results
  • Ability to provide future support/development
  • Cost of Ownership/ROI
  • Both quan titati ve and qualita tive value propositi on
  • Follow these best practi ces in order to make the right decision, and then be sure to set the stage for a successful implementati on by communica ting the decision and implementati on roadmap early to those who will be affected.

 

Click Here to read ‘Part 1’ of this ar ticle on Business Drivers of a Software Evaluati on.

Visit our Software Evaluation page for more informaon on EAG’s Software Evaluation service offering