The software development world is crowded with different practices, metrics, methodologies, tools and techniques. For example, metrics such as “number of open tickets”, “code coverage” or “release cadence” give us a numerical feel for how things are going, and methodologies such as Scrum, Waterfall and Lean give us different approaches to organising. 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 risks. Risk isn’t something that just appears in a report, it actually drives everything we
It may not be rigorously researched (the author admits as much in the intro), but it is nonetheless an interesting way of thinking about project management, particularly in the software context, but I can sense application in wider hardware-software contexts as well.