For ease of reference, Federico’s reasons are:

1) There is a focus on delivering what the customer needs (shock, horror!)

2) Creativity and innovation is increased (in my mind, it happens because all programmers are brought out of their comfort zones - hence triggering all of the “Five Discovery Skills of Innovation” - but particularly the networking aspect, including with customers & end-users

3) Processes are focused on delivering value (to which I would also add documentation, as a means of achieving shared understanding, not a Pulitzer)

4) Value is delivered early (and also surprises, as the hard bits are done up-front - not left till the end, or swept under the carpet).

5) Value is delivered sustainably

6) Value is the objective - as I keep repeating internally:
Value to the customer = Benefits - Cost (i.e. Price + Indirect)
Value to us, the supplier = Revenue - Our Cost
For both stakeholders, both pieces in the equation need to be taken into account.

I particularly like the reference to Jim’s suggested change to the traditional iron triangle, which always - to me - seemed a trite, defeatist cop-out, as it is assumed a uniform level of skill amongst all development teams. At least Jim’s triangle is an improvement - though it only goes part-way to addressing this shortcoming.