We see a sharp increase in collaboration, communication, and activities like pair programming.
However, we also have a pretty mature staff.
When building and sharing software for others (even internal others), you need to ensure there's a healthy understanding of builder and customer. When I've seen this pushed at less mature organizations, there was a tendency for many engineers to go off and start building tons of stuff that wasn't helpful.
You'll need to ensure people are using this to foster good conversation, and collaboration. It *wiil* cause some high friction conversations, but those help ensure the modules are being built the best way possible or serving the maximum good instead of just being some lone dev's pet project.
We see a sharp increase in collaboration, communication, and activities like pair programming.
However, we also have a pretty mature staff.
When building and sharing software for others (even internal others), you need to ensure there's a healthy understanding of builder and customer. When I've seen this pushed at less mature organizations, there was a tendency for many engineers to go off and start building tons of stuff that wasn't helpful.
You'll need to ensure people are using this to foster good conversation, and collaboration. It *wiil* cause some high friction conversations, but those help ensure the modules are being built the best way possible or serving the maximum good instead of just being some lone dev's pet project.