Risk and Issue Management Flashcards
Risk management process - 1st step
- Identification (recorded w/ ID number etc etc, assigned owner). helps us think about risks and encourages team to become aware of threats. Identified through brainstorming, interviewing, prompt lists, check lists, assumption analysis.
Risk Management Process - 2nd step
Analysis. ensures all risks assigned a priority and have clear view of risk exposure for project. prodvides clear measure of impact risk will have on project and gives detailed analysis. Use probability impact grid, how likely and how severe
Risk Management Process - 3rd step
Monitoring and escalation. keep an eye on developments. PM and sponsor to agree thresholds at which point risks need to be escalated for further review or action
Risk Management Process - 4th step
Response - means all risks have mitigation in place with clearly identified contingency and owner. Allows us to prepare for risks and figure out which actions need to be taken. Incorporate risks into WBS, budgets etc.
Risk Management Process - 5th step
Closure - stakeholders are properly informed, contingencies can be relinquished, future project is better informed. Signifies risk has matured and no longer needs attention. so close when no longer has potential to materialise or at project close
Types of risk
Threats and Opps
How to deal with threats
- Avoid, change project scope, proactive. 2. Reduce, either probability or impact, put risk response in place to reduce likelihood of occuring. 3. Transfer, move to someone elses risk register through insurance policy or contract. 4. accept. monitor, put contingency in place to accomodate risk if does occur
How to deal with opportunities
- Exploit, take advantage of consequences, change scope to maximise the opp, don’t enhance probability (too big a risk). 2. Enhance, make more likely to happen and more valuable when it does. 3. Share, seek others who can actively capitalise. 4. Reject, if opp worth too lttle or requires too much work
Issue management process 1st step
Logging and analysis. record issue into a log, ensure recorded and assessed so PM and sponsor aware of what happened (need to keep track for lessons learned)
Issue management process 2nd step
Escalation - all issues escalated to sponsor bc breached the tolerance level agreed between PM and sponsor. Sponsor can then escalate to steering board if required. Ensures support in place for PM and governance structure to support management of issues
Issue management process 3rd step
Assignment of actions - once plan decided, PM to assign actions to person or group best placed to address issue. Gives clearly defined responsibilities for each action, important bc ensures no action missed
Issue management process 4th step
Enact change control - any changes made bc of issue is captured, any changes that impact other areas of project are recorded and intergrated into planning
Issue management process 5th step
Close the issue - shows issue has been dealt with and is no longer a threat
Failings of issue management process
- PM thinks they can solve it, not recognising significance and not escalating. 2. failure to track an issue once escalated and ensuring its resolution. 3. lose track of ownership - means PM ends up trying to fix everything
Linear and risk/issues
Risks identified at start and assessed at beginning. Risk contingencies stablished at start and are static. As project progresses, more risks may arise and are logged. Issue management still be dynamic and flexible but amy be delayed as consider all options before re-baselining