Project Risk Assessment Questionnaire Template Page 7
ADVERTISEMENT
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15Put your
Project Risk Assessment Questionnaire Template
Put your
Rev. 2.0, 09/07/2003
logo here
organization
name here
Section II
Typical High-Risk Problems/Response Actions
High-Risk Factors/Potential Problems
Risk Response Actions
A5. The quality of current data is poor and difficult to convert:
Make sure that all the old data elements are
correctly mapped to the new system
More work to convert the old data to the new system
Test the conversion process out rigorously before
Scrubbed data may still cause problems in the new system
proceeding with final conversion
Data conversion problems can cause significant project delays
Determine if the cost and trouble associated with
the converted data is worth the value. Ask
whether the new system can start with new data
only.
Keep the old system around for some period to
access the old data
Spend the effort to manually clean up the old data
as much as possible before conversion
A6. Package implementation requires heavy customization:
Consider other packages
Customization brings added complexity to the project
Consider custom development
Making modifications may result in something else breaking
Cut back on the business requirements so that
customizations are not required
Customization can lead to poor performance
Get a firm estimate of the cost and duration of the
Customization can complicate migrating to newer releases
modifications from the vendor and build into your
overall work plan
Heavy customization may mean that the wrong package was
selected
Manage the vendor relationship to ensure all
needed work is completed on schedule
Package will probably take longer to implement
Make sure the sponsor has approved the
Customization will require more reliance on the vendor
customizations being proposed
Thoroughly test the modified package for
functionality and performance
Maintain a vendor log to track issues and
milestones
A7. Package implementation is a new product or release:
Schedule training on the package as early in the
project as possible
Greater chance of problems surfacing
Add an internal resource, or a consultant, with
More reliance on the vendor to ensure problems are corrected
prior product experience onto the project
quickly
Schedule a pilot test or a prototype to gain
Installation, testing, and deployment will take longer
familiarity with the package before full
implementation
Hard to know up front whether the package meets all the
business requirements
Establish agreements with the vendor stipulating
support level and problem resolution times
See if the project can be delayed until other
companies have utilized the product
Seek out other companies that have used the
product for their feedback and key learnings
B. Schedule
Put your organization name here
Page 7
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Business