A Pattern Language
Explanation of how Risk-First comprises a pattern language of risk patterns for use in software projects.
Explanation of how Risk-First comprises a pattern language of risk patterns for use in software projects.
People all have their own agendas. What do you do about that?
On avoiding mistakes that limit your options later on.
Why is it so hard to be understood?
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?
What is the point of a deadline? Do they serve a useful purpose?
Risks faced by depending on something else, e.g. an event, process, person, piece of software or an organisation.
Risks you face when providing features for your clients.
List of all types of risk discussed in Risk-First.
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.
Risks due to the following a particular protocol of communication with a dependency, which may not work out the way we want.
Scarcity Risk is about quantities of a dependency, and specifically, not having enough.
Specific dependency risks due to relying on software.
Making sense of risks faced by software projects.
A way to think about the risks you face on a software project.