I once learned that, when something annoys you, you should immerse yourself into it completely.…
Some people claim that agile software development is a risk management strategy.
Because all principles of risk management are nicely covered when you've implemented an agile process.
The International Organization of Standardization has identified the following principles of risk management in their draft of ISO 31000 “Risk management — Guidelines on principles and implementation of risk management”:
You can see that all principles of risk management, as required by ISO, are covered by standard agile project management processes. Of course, it requires that risks are identified by both the customer and the team, and made visible on the backlog and the task board. This also fits well with my previous blog entry (Risk Management = Banana Peels AND Dollar Bills), where I wrote that risk management not only covers problems (impediments), but opportunities (user stories) as well.
Some examples of risk management could be:
Every risk identified by the team and the customer is either a user story or an impediment. Risks are evaluated in every sprint meeting and every stand-up meeting, and the team, the Scrum Master and the Product Owner take appropriate measures to manage them.
That's why agile software development is a risk management strategy.
However, I have also good reasons to claim that agile software development is NOT a full risk management strategy. But that's a story for next week…
(images by hellosputnik and the fayj)
Twitter – Subscribe – Newsletter – Bookmarks
Latest, greatest and favoritest posts:
People Don't Listen
Three Levels of Control
How to Handle Many Simultaneous Projects