and 1 hour to get a review and PR approval, that means the wait to processing time ratio is 60/5=12, and flow efficiency is only 7.7%.»
With Pull Requests you see just a polished and thought-through end result.»
if everyone that is needed is immediately available to respond (by #mobprogramming for example)?»
for reviewing their PRs (or any other help they need), your problem is not people not prioritizing other people’s work and lack of “team player spirit”.»
by hiring more people, don’t be surprised to see the culture of ineffective parts of the organization eat away the culture of effective parts of the org, which doesn’t have a need to scale at such a rate.»
The more they ask for help the less they feel they are meeting that expectation.»
as measuring code coverage for a team doing TDD.»
Very often, for a mindset that emerged inside environments with big batches, it takes increasing the holding cost of inventory to start changing the belief system that was created as a workaround for the limitations of the system and served as its governing constraint.»
because you see more feedback and quality being built in than on big PRs (‘LGTM + Approve syndrome’).»
Bosses say “Does that make sense” … to get compliance.
Leaders ask “What didn’t make sense?” to invite discussion.