Organizations: clarify value

[amyjko]

I think this chapter is already organized well with very understandable words. However, I think it would be better if the author could have input a short explanation at the end of what are the "values" intended to be in the software. It clearly states in the chapter that "The first and most important concept is that even in software organizations, the point of the company is rarely to make software; it’s to provide value". But I as a reader could not find what is the value here.

My issue is that although the article mentions the concept of ‘value’ in these quotes and discusses it slightly more in the bullet point list of roles, it doesn’t really go further in defining what ‘value’ is in a software engineering context. Is ‘value’ how much people measure the worth of software, in terms of enjoyment of use/ease of use/how well the software does what it’s supposed to do/etc?. For instance, would services such as Google be considered ‘high value’ for the efficiency and speed that they perform on? Without a clear answer from the article, I’m unsure if my personal definition is correct.