anoviceuser

Thanks Steve for sharing this. I am sorry to hear about your condition. I am sure as you survived Big C, you will survive the small C as well. Take care and thanks.

Great work @dexterlang. Thanks for building it. I am already actively using it and really like it.

Thanks @rails. Really appreciate the clarification.

@1ba9115454, Really appreciate your inputs. Thanks.

@javamantra, Thanks a lot for your elaborate inputs. These are valuable insights.

Thanks.

@rails,

By "Make decisions easy to change later", do you mean, 1. Getting the Module structure of the system correct with well defined contracts between them so that they can be changed, updated independently of each other.

Thanks for your inputs.

@maps7, Thanks for your inputs.

Do you want to share any further insights about what factors you use to narrow down the choices about the correct ways? Similarly how do you go about managing the Constraints & Trade-offs - Do you change the scope? Do you negotiate to relax the constraints etc.

Thanks.

I agree this is an awesome post and a really great example of how every Root Cause Analysis needs to be done. I am also impressed by their incident response.