A necessary step in both selecting and implementing a package is detailing the technical requirements required to run the application. Identify the hardware/software environment, interfacing systems, operational and backup procedures, and other key technical requirements.
What data should you keep in a Data Warehouse and why? This form helps you identify the needed data and its associated characteristics in relation to your business requirements.
User involvement is key to designing an effective application and a good user interface. Give the business users a template of standards and procedures to follow so that they can describe how they do their work, including workflow, and thus how the application should work for them.
Compare conferencing packages by the features they offer and select the package that fits your needs.
Are you developing a billing system for your client? You've defined your business requirements and information architecture and must now report back to Management on the project status. Here's a model executive summary report.
Organize all of your Intranet content, user groups, risks, action items and responsible parties with this comprehensive chart.
Use this questionnaire to learn all about the client's motives for establishing an intranet and the current technical/organizational environment in which it will be set up.
Why does your client want to build an intranet and what content do they want to disseminate? Prioritize the goals, issues, risks and solutions for setting up and maintaining an intranet site.
How do vendors and their packaged applications stack up against each other? Use this evaluation spreadsheet to see how they fulfill your business and technical requirements.
You're about to conduct a pilot project using a packaged application. What documentation and files will you need to do it right?
|
Work like you don't need the money, love like you've never been hurt, and dance like there's nobody watching. |
