5 ms·
I'm in a home team (not at Amazon) that wants to make our domain easier for away teams to work in. Aside from writing good documentation, what else can we do t
by jawns 3y ago
I'm in a home team (not at Amazon) that wants to make our domain easier for away teams to work in. Aside from writing good documentation, what else can we do to make it a hospitable environment without it becoming a drain on our resources?
- skellera 3y agoCreate IDE configs and other guardrails to limit churn and discussions on already determined style for your team. Clear goals and acceptance criteria.
- Others 3y ago1. Exercise good judgment about what projects are “away team-able”. Be okay saying “this needs to be done by our team” even when that’s hard. Otherwise you’ll end up with tricky features implemented by people who don’t understand the full context (this sucks very badly) 2. Make sure the amount of process matches the amount of complexity. If the change is very simple or only a few lines, make it trivial to submit code changes that will pass review. (So have really good automated style checks/test suites.) If the change is complex, make sure you’re doing design reviews before implementation, to ensure the away team doesn’t waste time with bad implementation strategies