Ha! Option A sounds like a classic case of 'over-engineering'. Increasing feedback loops and giving teams resources is good, but it's not the essence of 'locality and simplicity'.
Hmm, I'm not sure about option C. Understanding what customers are willing to pay for is important, but it doesn't seem directly related to 'locality and simplicity'.
I believe A) increase the feedback loops in the process and give teams the resources they need to fix problems is also a good example of locality and simplicity.
I think option B is the best example of the DevOps ideal 'locality and simplicity'. Focusing on the resources within the team's control and designing loosely coupled services seems to really capture the essence of that principle.
Felix
14 days agoCorinne
24 days agoYuriko
29 days agoMy
1 months agoSharita
6 days agoLenora
16 days agoEric
20 days agoNoelia
1 months agoMerlyn
1 months agoTamala
1 months agoRefugia
1 months agoRoslyn
17 days agoEmogene
20 days agoMitsue
2 months ago