Software industry: Difference between revisions
link |
Added write up on "Evaluation of software vendors for IT projects" |
||
| Line 44: | Line 44: | ||
| isbn = 0-262-13432-2 | | isbn = 0-262-13432-2 | ||
| author9 = David G. Messerschmitt and Clemens Szyperski}}</ref> | | author9 = David G. Messerschmitt and Clemens Szyperski}}</ref> | ||
== Evaluating software vendors == | |||
When an organization is looking for software vendors, the following things can be considered. | |||
# Core competency of the vendor - For example, when an organization is looking for ERP implementation vendors it would certainly be beneficial to go for vendors who specialize in these projects. However giant IT companies could be an exception as they specialize in multiple technologies. | |||
# Number of years in business - This helps organization understand the credibility of the business. | |||
# Stock market listing - Important if the size if the project is huge as a listed software vendor is more likely to have better governance processes | |||
# Overall and available vendor headcount - This can help organizations to decide how their resources requirements can be met by the software vendor. | |||
# Vendor credentials - The software vendor's prior experience in similar projects can increase the confidence of the organization | |||
# Industry Certifications/awards/Alliance partners - Industry recognition is another parameter for evaluating the software vendors | |||
# Local and global offices - While local office is important for any meetings, follow ups etc. global offices show the reach of the vendor | |||
# Project management/tracking processes - More robust the processes are, better will be quality of the software product | |||
# Lead times to start development - The vendor might have a lot of projects on hand already and it is important for an organization to know the lead times | |||
# Core solution and solution options - The software vendor should be made to make a presentation to showcase vendor's understanding of the requirements | |||
# Development time and costs - The estimates for efforts, resources, schedule and costs (includes fees and expenses) | |||
# Non functional requirements - The vendor's ability to meet non functional requirements | |||
# Warranty support agreements - For post production break fixes | |||
# Post go live - Maintenance activities support costs | |||
These are just some of the typical parameters used for evaluating the software vendors for different projects. | |||
Depending on the specific project requirements, an organization can add/modify the parameters. | |||
== See also == | == See also == | ||