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
11 months agoJackie
11 months agoHoa
11 months agoCorinne
12 months agoSlyvia
10 months agoArdella
10 months agoLauran
10 months agoLeah
11 months agoYuriko
12 months agoMy
1 years agoSharita
11 months agoLenora
12 months agoEric
12 months agoNoelia
1 years agoMerlyn
1 years agoTamala
1 years agoRefugia
1 years agoRoslyn
12 months agoEmogene
12 months agoMitsue
1 years ago