Scrum, Waterfall, Lean, Prince2, DevOps: what do they all have in common?
One perspective is that they are individual software methodologies, offering different approaches on how to build software.
However, here, we are going to consider a second perspective: that building software is all about managing risk, and that these methodologies are acknowledgements of this fact, and they differ because they have different ideas about which are the most important risks to manage.
Hopefully, after reading through some of the articles here, you’ll come away with:
- An appreciation of how risk underpins everything we do as developers, whether we want it to or not.
- A framework for evaluating software methodologies and choosing the right one for the task-at-hand.
- A new way to look at the software development process: it’s an exercise in managing different kinds of risk.
- The tools to help you decide when a methodology is letting you down, and the vocabulary to argue for when it’s a good idea to deviate from it.
- Risk-First is a Pattern Language (think Design Patterns, or TVTropes)
- “Software Development Is All About Risk” - Kent Beck
- Who Is This For?
- Quick, High-Level Summary
- About The Menagerie (Print & Kindle Editions)
If you feel something important is missing, or you spot a mistake, we need help.
Although this is a collaborative Github project, it’s not meant to be an open-ended discussion of software techniques like Ward’s Wiki. In order to be concise and useful, discussions need to be carried out by either:
- Opening an Issue.
“Star”ing the project: this will cause you to be invited to join the Risk-First organisation
- List of Contributors
An introduction to the concept that managing risk underpins all activity on projects.
Risk management theory around evaluating risk, e.g. Eisenhower's box, NPV, Discounting.
Add Your Star On GitHub to receive an invite to the GitHub Risk-First team.