|Risks due to the commitments we make around dependencies, and the limitations they place on our ability to change.
|Risks due to the fact that things you depend on have agency, and they have their own goals to pursue.
|Risks due to the inadequacy of the physical channel used to communicate our messages. e.g. noise, loss, interception, corruption.
|Risks due to the difficulty of communicating with other entities, be they people, software, processes etc.
|The specific risks to a project of having a large, complex codebase to manage.
|Risks caused by the weight of complexity in the systems we create, and their resistance to change and comprehension.
|Risk that the software you provide is too complex, or doesn't match the expectations of your clients' internal models.
|Risks that a group of agents cannot work together in a mutually beneficial way, and their behaviour devolves into competition.
|The risk that a particular approach to a change will fail. Caused by the fact that at some level, our internal models are not a complete reflection of reality.
|Where the use of a dependency has some kind of deadline, which can be missed.
|Risks faced by depending on something else. e.g. an event, process, person, piece of software or an organisation.
|Risks due to some clients not having access to some or all of the features in your product.
|Risk that the features required by clients will change and evolve over time.
|Risks you face when providing features for your clients.
|Risk that the needs of the client don't coincide with services provided by the supplier.
|A particular scarcity risk, due to lack of funding.
|Risk that the functionality you are providing doesn't match the features the client is expecting, due to poor or partial implementation.
|Risks arising from insufficient or erroneous internal models of reality.
|Risks caused by the choice of abstractions we use in communication.
|Risks due to the difficulty faced in updating an internal model.
|Risks due to the differences between reality and the internal model of reality, and the assumption that they are equivalent.
|Risk that the value your clients place on the features you supply will change, over time.
|Risks caused by the difficulty of composing and interpreting messages in the communication process.
|Risks of losses or reputational damage caused by failing processes or real-world events.
|Risk that a particular set of market conditions.
|Risks due to the fact that when dealing with a dependency, we have to follow a particular protocol of communication, which may not work out the way we want.
|Risks due to the failure of encoding or decoding messages between two parties in communication.
|The general risk that the competitive environment we operate within changes over time.
|Risk that the functionality you provide changes for the worse, over time.
|Risks of not getting benefit from a dependency due to it's reliability.
|Risk of not being able to access a dependency in a timely fashion due to it's scarcity.
|The aspect of dependency risk related to time.
|Agency Risks due to actors from outside the system.
|Dependency Risk due to software dependencies.
|The aspect of dependency risks related to employing people.
|Risk that a party we are communicating with can't be trusted, as it has agency or is unreliable in some other way.