The software development world is crowded with different practices, metrics, methodologies, tools and techniques. But what unites them all?
The Risk-First perspective is that all of these practices and methodologies have at their heart the job of managing different software development risks. Risk isn’t something that just appears in a report, it actually drives everything we do.
Risk-First is split into three main parts:
However, if you want a brief overview of what this is all about, the articles in this section give you a short taster.
In particular, if you’re after a very high-level summary, please check out the Quick Summary article below.
If you like what you’ve read here, then dive into Part 1
Argument that software development is all about risk, as originally made by Kent Beck.
Explanation of how Risk-First comprises a pattern language of risk patterns for use in software projects.
Risk-First is for software development teams, including software developers, managers, testers and technical leads.
Add Your Star On GitHub to receive an invite to the GitHub Risk-First team.