Organizations: elaborate on risk

[amyjko]

This chapter was a cool insight at the larger picture of an organization. I wish it went into more detail about how risk can be measured and seen quantitively. I'm curious to know who is at fault if a software fails but the engineers wrote the code perfectly as they were described by the designers. Additionally, if the engineers foresee the software failing, do they have an option to voice their opinion in this situation? In the chapter it seems that engineers should just focus on writing their code and making it run well.

In the article, the author says every decision made in a software team is under uncertainty. But I didn’t see a lot of narrative about the decision-making process in the article. As someone who is not in the software engineering field, I would like to know more about how are decisions made in the field? What situation does the software team need to consider while making the decision? What is the main considerations while the team making the decision? I think it would be better that I could get more background information while it comes to decision making in the field of software engineering.

I think one aspect that could be improved is adding more specific examples. For example, on the section about risk, the last sentence talks about the reason why software fails, but the section does not give a specific example of a software that failed. I think by having this example it would give me a better understanding of a situation of how a software was "told the wrong thing".