High transaction cost incentivizes for big batches. And lack of availability (long waiting times) drives transaction cost up. I.e. the more something is rare to find, the more valuable it’s perceived as.
»one line of code change that is reviewed immediately.
»but an inevitable consequence of a desire to drastically tighten the feedback loop to review and integrate the code and ideas.
»that you annoy reviewers so often that they just give up and join you in a pairing session instead.
»Long waiting times in the system incentivize increase in WIP.
And, the higher the WIP, the longer the waiting times will be.
processing time will get shorter as well because the feedback gets incorporated faster.
»Shift in “outcomes over outputs” takes away power from people that used to have monopoly on defining solutions and next steps.
»is (most probably) caused by:
»One more in “it’s not about X. It’s about about Y” series.
»It’s not about long-lived branches per se that’s an anti-pattern. It’s about coding in isolation for too long without getting the feedback.
»