in original system implementation and whenever there is a change in user interface, functionality, or technical infrastructure. The table below highlights the additional risk considerations for egovernment applications. Exposure Risks (User Interface) High
E-Risks (Infrastructure)
Low
High
Reduce e-risks by increasing testing scope to reduce risks of instability and volume overload, testing contingency and rollback plans, etc.
High
Low
Increase testing to reduce risks of functional failures, provide mock-ups of screen design to user community, test on focus groups, etc.
Low
Low
No additional action
High
Possible Mitigation Action Take action to reduce both by increased testing, prototyping, focus groups, low profile introduction of site or application, etc.
Responsibility for project risk management must be assigned to a senior member of the project team, and this person must accept full accountability for the performance of the risk management function. The larger the project, the greater the chance for failure; therefore, the more effort you need to put into managing risks. Projects costing less than $750,000 have 46% of being fully successful, while those costing over $10 million have only a 2% chance of being successful. For bigger projects, it is essential to identify points of failure before they bring down the whole project. Stoplight charts may be used as a means to report the specific status of problems and risks within a project. There should be two forms of these charts presented at project reviews: a problem chart or a set of problem charts and a set of risk charts. The problem charts should truly treat problems as red if they are affecting the project and have not been dealt C:\Documents and Settings\pfink\Local Settings\Temporary Internet Files\Content.IE5\UT87UX65\Statewide Implementation Framework - Best Practices and Standards.doc Page 58 of 148