This pattern refers to the work behavior of repeatedly working privately๐ and hoarding all work in progress to deliver one giant pull request at the end of the sprint.
The more an individual saves up their work, the less they collaborate with others.
Working alone is inherently riskier than working with others.๐
Submitting work all at once can lead to lower quality code โ both from:
โ๐ญ๐ก๐ ๐๐ฎ๐๐ฆ๐ข๐ญ๐ญ๐๐ซโs standpoint (๐คโ๐ ๐๐๐๐โ๐ก ๐โ๐๐๐ ๐๐ ๐กโ๐๐๐ ๐ค๐๐๐ ๐๐๐๐๐ฆ ๐ก๐ ๐๐๐ก ๐๐๐๐๐๐๐๐ ๐๐ ๐๐๐ก๐๐๐ ๐๐๐ก๐๐๐ก๐๐๐ ๐๐๐ ๐ ๐ก๐๐๐ ), andย
โ๐ญ๐ก๐ ๐๐๐ฏ๐ข๐๐ฐ๐๐ซโs perspective (๐คโ๐ ๐๐๐๐๐๐ฆ ๐๐๐๐ ๐โ๐ก โ๐๐ฃ๐ ๐๐๐๐ข๐โ ๐ก๐๐๐ ๐๐ ๐๐๐๐๐๐ฆ ๐ก๐ ๐๐๐๐๐ข๐๐ก๐๐๐ฆ ๐๐๐ฃ๐๐๐ค ๐๐๐ ๐๐ ๐กโ๐๐ก ๐๐๐๐).
๐๐จ๐ฐ ๐ญ๐จ ๐ซ๐๐๐จ๐ ๐ง๐ข๐ณ๐ ๐ข๐ญ
Large and infrequent commits can be a sign that the engineer is working privately until their project is finished,ย
and then submitting their work all at once.
๐๐ก๐๐ญ ๐ญ๐จ ๐๐จ
Above all else, be compassionate.๐ค
Odds are, youโve recognized this pattern right before or just after the end of a sprint,
so these engineers are likely tired, stressed, and worn out.๐ฉ
Make sure they get the time and space they need to recover from delivering such a big payload.
This can be great timing for an impromptu and informal 1:1.๐ฃ
Bring up the topic of team collaboration, and how saving work until itโs completed leaves little room for learning from others throughout the process. ๐ก