Here, we’re going to take you through the various types of Risk you will face on every software project.
In Thinking Risk-First, we saw how Lean Software Development owed its existence to production-line manufacturing techniques developed at Toyota. And we saw that the Waterfall approach originally came from engineering. If Risk-First is anything, it’s about applying the techniques of Risk Management to the discipline of Software Development (there’s nothing new under the sun, after all).
One key activity of Risk Management we haven’t discussed yet is categorizing risks. So, this track of Risk-First is all about developing categories of risks for use in Software Development.
After reading this section of Risk-First, hopefully you will:
- Appreciate the different kinds of risk you face on software projects, and how to identify them.
- Learn a Pattern Language: that is, a vocabulary of terms which you can use for discussing these risks with colleagues.
- Know the main actions you can take to handle each type of risk.
Explanation of how Risk-First comprises a pattern language of risk patterns for use in software projects.
Risks due to the difficulty of communicating with other entities, be they people, software, processes etc.
Risks caused by the weight of complexity in the systems we create, and their resistance to change and comprehension.
Risks faced by depending on something else, e.g. an event, process, person, piece of software or an organisation.
Scarcity Risk is about quantities of a dependency, and specifically, not having enough.
Risks due to the following a particular protocol of communication with a dependency, which may not work out the way we want.
Risk due to the choices we make around dependencies, and the limitations they place on our ability to change.
Explanation of Agency Risk and ways to mitigate it through monitoring, security and goal alignment.
Risks that a group of agents cannot work together and their behaviour devolves into competition.
Risks of losses or reputational damage caused by failing processes or real-world events.
Add Your Star On GitHub to receive an invite to the GitHub Risk-First GitHub team for new article notifications and discussion.