Cover Legal/Regulatory Risk

[robmoffat]

This needs to be mentioned in slightly more detail (with examples) on the Operational Risk page.

[HeroicHitesh]

@robmoffat Is this issue still relevant? If yes, can you provide more details?

[robmoffat]

Hi Hitesh,

Yeah, I think it is still relevant, but I'm not sure I'm the right person to write this. From an Operational Risk perspective, it's quite possible to have a product that works perfectly, fulfils user's requirements (Feature Risk) etc. but nevertheless could fail because it doesn't consider Legal/Regulatory Risk aspects.

A good example might be a new model of a car, which could work perfectly, but doesn't pass national safety requirements and therefore is not allowed to be sold.

From a software perspective, cryptocurrencies like Bitcoin are an interesting case. In many jurisdictions, Bitcoin is illegal. However, it mitigates this Legal Risk by distributing control so widely that it cannot be banned by authorities. I guess this shows that complying with law and regulation is not the only mitigation for Legal & Regulatory Risk.

From a product development perspective, this is addressed with techniques like PESTLE Analysis.

thoughts?

[HeroicHitesh]

Hi Rob Moffat,

TBH I myself am not the write person to write the content of this type, as I have no idea regarding this topic, although I was hoping that the contributor is supposed to insert some text on Risk Analysis in some appropriate place.
So, I guess this issue is not suitable for me.

thoughts?

To be frank, all this makes little sense to me, but if provide me the exact content required to be added here or here, I am ready to take up this task.

Thank you

[robmoffat]

The basic premise is that all activities in a software project are managing risk in one way or another. The current status is that I've done a lot of the work breaking down the kinds of risk that affect software projects. e.g. Operational Risk, Complexity Risk, Dependency Risk etc.

However, there's lots more to do! If you have any useful experiences that you feel could fill an article, I'd be happy to take a contribution and integrate it on the Jekyll site.

Alternatively, if you want some ideas where to start, nothing in this directory has been written yet:

https://github.com/risk-first/website/tree/master/practices

It's supposed to cover the practicalities of how, say, Documentation manages risk on a project (e.g. reducing Coordination risks).

I am working on some interesting new contributions which I hope will see the light of day in 2020...