website

I agree, maybe it does _sound_ depressing. But the food you eat and air you breathe _are_ based on risk! Our bodies try to warn us about the bad air and food by making it smell/taste bad. You can go ahead and eat it if you want! I agree with you that it's nice that our bodies make things _nice_ to eat as well as recognising nasty stuff. I wonder if there is an evolutionary reason for that too... Sadly, there are still some things that _don't_ taste bad but will kill you... hidden risks of eating I guess. I talk about Complexity Risk here: https://github.com/risk-first/website/wiki/Complexity-Risk Often, Complexity is fine, but then something bites you in the ass unexpectedly. Sounds like risk to me.

These risks get a lot of coverage in Risk-First: - https://github.com/risk-first/website/wiki/Communication-Ris... - https://github.com/risk-first/website/wiki/Complexity-Risk#c... - https://github.com/risk-first/website/wiki/Coordination-Risk

Updated it for you: https://github.com/risk-first/website/wiki Using plain english is harder than it sounds! :)

Hi Mikekchar, Thanks so much for your feedback. Addressing each point in turn: 1. UAT/Integration: this was just an "example process", one that you _might_ follow. YMMV and you could get better results doing things in a different order or with extra steps. The point was to show that each step on your process (whatever it is) is meeting reality and managing risk. I'm with you on this: you should _totally_ prepare for UAT ahead of doing it, because that preparation actually manages risk too - the risk of the users not knowing what to test, or not being available, or not understanding the functionality, or the data not being right etc. 2. On "Do the simplest thing... and refactor": this (and YAGNI) are great "rules of thumb" about how to develop. What I'm trying to do here is explain _why_ they are great. That is, explain how they