CLARIFY YOUR REQUIREMENTS:
Know your business objectives and mid to long term goals for the web site. Express them as Business Requirements to be sure you have scalability, localization, internationalization, accessibility and cross-browser compatibility in tow.
Know your functional specs and express them as critical use cases. Be clear about what if must do, for how many at a time, how fast.... etc.
To 'rate' the vendor, listen for questions. If they are asking question they either aren't listening or have already made up their minds, neither of which is a good indicator for you.
HOW WILL YOU KNOW IF IT IS ANY GOOD?
What is the vendor's test methodology? Functional testing, load testing, usability testing? How has it been done in the past (by the prospective vendor)? Look for certification: HFI Certified Usability Analyst or CPE/CHFP certifications. Are their testing tools ones that you have experience with and can use in the future?
HOLD THE VENDOR'S FEET TO THE FIRE, BUT PAY FOR EXCEEDING EXPECTATIONS, TOO.
Consider a risk/reward contract where missed deliverables have consequences that hurt.
What is their preferred development process? Agile? Waterfall? Iterative waterfall, etc. How does that match you company process? Process matching is often as important as technology matching.
Insist to standards based development but most important get documentation that is clearly written and comprehensive.
HOW WILL THIS FIT INTO YOUR HOUSE?
What are the core technologies you use? How will the solution integrate? New technology means increases in total cost of ownership.
Request an integrated implementation and training proposal. Who will do what?
In the training proposal look for thoughtful 'user skill' analysis.
EVERY KID WANTS A PUPPY BUT WHO WILL WALK THE DOG?
Know your internal resources skills. What skills will be needed to keep the site going? Do you have them? Would a different technological approach align with your needs?
Watch for skills transfer support if it is needed, don't short yourself here. The site developer may not be qualified to provide the training but they should be able to tell you, in detail, what skills and technical knowledge will be needed. If it is needed, will the cost to 'get ready' be significant? Will the time to build the skill be significant? Is there enough time?
Site maintenance and ease of use for the CMS component are foundational to 'the day after' impacts.
If you expect post-project support get a detailed SLA.
Slashdot Mirror
CLARIFY YOUR REQUIREMENTS: Know your business objectives and mid to long term goals for the web site. Express them as Business Requirements to be sure you have scalability, localization, internationalization, accessibility and cross-browser compatibility in tow. Know your functional specs and express them as critical use cases. Be clear about what if must do, for how many at a time, how fast .... etc.
To 'rate' the vendor, listen for questions. If they are asking question they either aren't listening or have already made up their minds, neither of which is a good indicator for you.
HOW WILL YOU KNOW IF IT IS ANY GOOD?
What is the vendor's test methodology? Functional testing, load testing, usability testing? How has it been done in the past (by the prospective vendor)? Look for certification: HFI Certified Usability Analyst or CPE/CHFP certifications. Are their testing tools ones that you have experience with and can use in the future?
HOLD THE VENDOR'S FEET TO THE FIRE, BUT PAY FOR EXCEEDING EXPECTATIONS, TOO.
Consider a risk/reward contract where missed deliverables have consequences that hurt.
What is their preferred development process? Agile? Waterfall? Iterative waterfall, etc. How does that match you company process? Process matching is often as important as technology matching.
Insist to standards based development but most important get documentation that is clearly written and comprehensive.
HOW WILL THIS FIT INTO YOUR HOUSE?
What are the core technologies you use? How will the solution integrate? New technology means increases in total cost of ownership.
Request an integrated implementation and training proposal. Who will do what?
In the training proposal look for thoughtful 'user skill' analysis.
EVERY KID WANTS A PUPPY BUT WHO WILL WALK THE DOG?
Know your internal resources skills. What skills will be needed to keep the site going? Do you have them? Would a different technological approach align with your needs?
Watch for skills transfer support if it is needed, don't short yourself here. The site developer may not be qualified to provide the training but they should be able to tell you, in detail, what skills and technical knowledge will be needed. If it is needed, will the cost to 'get ready' be significant? Will the time to build the skill be significant? Is there enough time?
Site maintenance and ease of use for the CMS component are foundational to 'the day after' impacts.
If you expect post-project support get a detailed SLA.