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:
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:
Some easy-to-digest ideas that will set the scene for examining the practices later.
Risks are often very similar across different software projects. And, if you know about them, you can look for them. This section attempts to break them down for you:
This part is a discussion of the different practices within Software Development, and how they mitigate and accentuate the different risks.
A more in-depth look at software methodologies and how their chosen practices reflect their position on what the most critical risks are.
A more light-hearted collection of blog posts related to the software development process, aiming to use what we’ve learnt in real-life contexts.
Found this interesting? Please add your star on GitHub, thanks.