agile projeCTs do not magically manage risks for us! agile’s short cycles and regular feedback might seem to have a risk management approach naturally built into the process. after all, the building blocks and attachment points for plugging in an effeCTive risk management process are present. However, building software inCRementally does not ensure risks are identified and managed. In short, agile is not about risk management, at least not in the broadest sense.
We need to exert some effort – but the agile process does help provide some good spaces where we can injeCT risk management aCTivity, and outlines a couple of praCTical tools that can be used to start improving risk management approaches.
agile provides processes and mechanisms that we can leverage for effeCTive projeCT risk management. For example, the frequent change requests and reprioritization of the backlog provides an opportunity to insert risk avoidance or risk mitigation aCTions. another example is the use of regular retrospeCTives that review progress and process as an opportunity to examine the effeCTiveness of risk management strategies and take correCTive aCTions. Finally, daily standup meetings can also be used to identify as early warnings for potential new risks, or identifying if a risk has been triggered.
ProjeCT risk management has some parallels to the formal requirements process. Like the development of detailed requirements documentation, projeCT risk management may seem out of step with the paradigm of agile projeCTs. However, just as requirements are necessary, risk management is also necessary. This is one of the reasons why so many projeCTs use a sort of ‘hybrid’ approach, combining the appropriate amounts of agile and waterfall to get the projeCT done right. This gives a lot of CRedence to the idea that risk management is needed on agile projeCTs.
The key is to get the whole team to take a risk-based view of projeCT work in addition to a produCTion-based view. Each agile ceremony, checkpoint or meeting, as they happen according to the presCRibed cadence of the projeCT, needs to include serious attention to examining risks as well as to-do’s. This may involve some retraining to orient everyone to this vital funCTion.
Risk management is CRitical for every projeCT, including agile projeCTs. However, it does take some effort. With a little training to raise awareness, risk management on agile projeCTs can become part of the process and can be an effeCTive team effort. Using techniques like a risk-adjusted backlog, risk retrospeCTives and discussions of risks in daily standup meetings, you and your team can effeCTively manage risk on agile projeCTs.