The document discusses risk management in software project management. It defines risk as something that has not happened but could have a negative or positive impact. It then outlines the risk management discipline and principles from the Microsoft Solutions Framework, including staying agile, open communication, and learning from experiences. The document stresses that risk management should be practiced throughout the entire project lifecycle using tools like risk identification checklists, risk registers that are regularly updated, and by ensuring risks drive project activities. It concludes that risk management is one of the most important aspects for development leads.

1. Adam Gilmore

2.  What is a risk?
 MSF Risk Management Discipline
 Services Delivery Methodology (SDM)
 Conclusions
 Resources

3.  Something that hasn’t happened
 Negative (or positive) impact on the project
 Issues are risks that have happened

4.  MSF Foundational Principles
◦ Stay agile, expect and adapt to change
◦ Foster open communications
◦ Learn from all experiences
 Unemotional way of communicating concerns
 Allows you to take risks

5.  Risk Management Process

6.  Risk Identification Checklist
 Risk List

7.  Was there a risk register when you started the
project?
 Is there a risk plan?
 Do you have regular risk reviews?
 Does the risk register get updated?
 Are all of the team raising risks?
 Do risks drive your activities?

8.  Risk management is about looking ahead
 Do risk management all of the time
 Use the SDM templates
 Focus on the high-exposure risks
 Mitigations cost
 Agile methods are all about risk management
– they’re risk-driven
 IMHO risk management is the most important
aspect of the dev lead role

9.  Software Project Survival Guide, Steve McConnell
http://www.stevemcconnell.com/sg.htm
 David Anderson’s blog
http://www.agilemanagement.net/Articles/Papers/
Agile2009-NewApproachesto.html
 SDM (download the SDM portable library)
http://infoweb2007/sites/sdm/pages/default.aspx