Possible Risk Reduction Strategies Risk Reduction Strategy Poorly

Possible Risk Reduction Strategies Risk Reduction Strategy Poorly defined objectives Reconfirm what organizations mission and/or business goals are then ensure IT solution aligns to that. Does client have an existing IT Team and/or Budget for IT? Report to client on skills needed to maintain application and potential future costs plan for IT. Also focus on maintainability over function. System not focused on organizational objectives Revisit Root Cause with client to confirm we’re solving problem System requirements are unclear Consider intensive prototyping session or creating an MVP Unstructured system procedures Document the procedures with a top-down structured tool, such as DFDs or Business Process Flows. Multiple business areas involved Conduct a JAD session with managers from each organizational unit. JAD = Joint App Design Project estimated at longer than 3 months Subdivide the project into smaller projects. Focus just on must haves System uses unproven technology Use iterative prototyping to prove the technology as an MVP while the design evolves. Multiple system sites involved Implement the system with a pilot installation or a phased approach. Developers inexperienced in methodology Have developers work closely with experienced practitioners Developers unskilled at determining functional requirements Train developers in SDLC frameworks. Make user part of requirements creation and signoff. Developers unfamiliar with information technology architecture Have developers work closely with experienced developers and utilize self-study materials. Be specific on resources to be used Users have little business area experience Build system with clear process and instructions baked into design Users have little system development experience Conduct on-site classes in system methodologies. Users are uncommitted to the project Conduct JAD sessions with committed top-level managers present. Have plan for client leadership to communicate purpose of project. NOTE: It’s one thing to write these down, it’s another to do it. Make sure you really can accomplish a strategy before saying you’re going to use it.

Risk Score Spectrum High Medium Lower -17 to -7 -6 to 6 7 to 17 Important Reminders/Tips: • The goal of this exercise is not just to identify the risks and be done. Your team should be sure to address risks with a reduction strategy. • Ideally your overall risk score should go down if your reduction plans are working or at least remain static • Each week in your team meetings you should rescore/review the risk matrix and then ask yourself if the risk is being properly managed