I love this one. I never understood why management tools have to be boring. They must be effective, and without a good communication tool, it is often just a good intellectual exercise.
I have often enhance business results by changing the way it is communicated.
I could write a long essay on what I don’t like about many business documents. Often, it is as if the analysis is more important than communicating the analysis and obtaining actions and results. So seeing this post is indeed refreshing.
Written by Jesse FewellFriday, 24 August 2012
Last week at Agile 2012, there were a couple Risk Management talks that blew my mind. I was already comfortable with the notion that Agile methods offer a set of effective IMPLICIT risk management practices (e.g. iterative learning cycles, fully tested iteration increments). But this past week, I learned the community is beginning to mature a set of EXPLICIT risk management practices that can be embedded in your Agile methods.
Mike Griffiths shared his experiments with using collaboration games to improve Risk Management practices. He has a multi-part blog series that goes through the approach in detail, but the most important can be summarized in 3 points. Meanwhile, LeadingAgile’s very own Dennis Stevens had a talk where he challenged people to move beyond 1-dimensional thinking. Here is my summary of the key points from both talks.
Make risk planning more engaging. In his talk, Mike asserted that we need to get beyond the idea that Risk Management has to be boring academic exercise. He does this by renaming the standard risk management processes to be more playful. “Risk Identification” becomes “Find Friends and Foes”. “Qualitative Risk Management” becomes “Post Your Ad”, where risks look more like a job board. This helps us get over the anxiety of being perfect or technically correct.
Make risk planning more holistic. Dennis suggested we involved multiple disciplines in risk analysis, rather than just the ivory tower project manager. Technical people, operations people, HR people, all need to be a part of the conversation. He also highlighted our tendency to go straight into the weeds (“IF the shipment of servers is late, THEN our testers will be late getting started”). Instead, Dennis proposed a multi-tiered taxonomy for thinking about risk at progressively higher levels. Specifically, a Risk Category (e.g Security) will cover many different Risk Drivers (e.g. Fraudulent Transactions), which will in turn unearth the Risk Events (“IF a customer deposits More people thinking about risk at more levels.
Think of risk at multiple levels
Make risk planning more visual. Mike shows a few examples of hands-on collaboration games for performing the risk management processes. This moves the risk conversation into a more whole-brained activity, where both left and right hemisphere activities are engaged. Also, it keeps the risks front-and-center in our minds as we perform the project, rather than having them archived in a spreadsheet somewhere.
Team’s visual brainstorm of risks
What about you: What EXPLICIT risk management techniques do add into your Agile projects?