Upload
felipe-dornelas
View
234
Download
2
Embed Size (px)
Citation preview
“Organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations”
— Melvin Conway, 1968
3
LET’S IMAGINE THIS SCENARIO
6
• Distributed UK and Brazil teams • UK team are clients • Brazil team are contractors • Need to build a big service
COMMUNICATION ISSUES
13
• UK makes decisions • Brazil is not invited to all meetings • E-mail communications • Separate time zones
INFRASTRUCTURE DOES NOT HELP
14
• Phone conferencing sucks • No video • Chat apps blocked by firewall
FRUSTRATIONS
20
• Siloed knowledge • Poor productivity • Code quality is sacrificed • Over-engineered distributed monolith
DROP BY FOR A VISIT
28
• Meet everyone face to face • You won’t be just an avatar anymore • Understand the organization culture
MAKE A TRAVEL SCHEDULE
33
• Rotate travel among the team • Have someone from your team onsite • Bring the client to visit your office!
CONFERENCING
36
• Internet bandwidth is critical • Turn the video on • Good audio equipment • Phone line can have degraded audio
CHANGE YOUR ATTITUDE
46
• Use the audio video link as much as possible • Participate in the team chat • One or two quick daily stand-ups • E-mail as a last resource
CORE HOURS
51
• Agree upon core hours • Let the team know when:
• You are going to be late • You will leave your desk for too long
• It’s all about perception!
CROSS-FUNCTIONAL TEAMS
57
• Vertical stories • Understand the whole stack • Work on all modules • Share knowledge
CONSULTING ADVICE
60
• Have someone onsite as a contact point • Ask for help • Don’t let the client forget to invite you to meetings