32 docs tagged with "Risks"

Risks due to the inadequacy of the physical channel used to communicate our messages. e.g. noise, loss, interception, corruption.

Why is it so hard to be understood?

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 caused by the difficulty of composing and interpreting messages in the communication process.

Risks due to the failure of encoding or decoding messages between two parties in communication.

Risk that a party we are communicating with can't be trusted, as it has agency or is unreliable in some other way.

A lot of advice around constructing software comes back to simplicity. Why?

What prevents us working as a team? Why are distributed systems so hard?

People all have their own agendas. What do you do about that?

Risks due to the commitments we make around dependencies, and the limitations they place on our ability to change.

What is the point of a deadline? Do they serve a useful purpose?

Risk faced by depending on something else, e.g. an event, process, person, piece of software or an organisation.

Risks due to the following a particular protocol of communication with a dependency, which may not work out the way we want.

Risks of not getting benefit from a dependency due to it's reliability, either now or in the future.

A particular scarcity risk, due to lack of funding.

The general risk that the competitive environment we operate within changes over time.

Scarcity Risk is about quantities of a dependency, and specifically, not having enough.

A particular scarcity risk, due to lack of time.

The aspect of dependency risks related to employing people.

Specific dependency risks due to relying on software.

Risk you face when providing features for your clients.

Risks due to the differences between reality and the internal model of reality, and the assumption that they are equivalent.

Risks of losses or reputational damage caused by failing processes or real-world events.

Risk that the software you provide is too complex, or doesn't match the expectations of your clients' internal models.

Risk of not being able to access a dependency in a timely fashion due to it's scarcity.

Risk that the features required by clients will change and evolve over time.

Risk that the needs of the client don't coincide with services provided by the supplier.

Risk that the functionality you are providing doesn't match the features the client is expecting, due to poor or partial implementation.

Risk that the value your clients place on the features you supply will change, over time.

Risk that the functionality you provide changes for the worse, over time.