4 ms·
“Innovation teams shouldn’t be burdened with operational concerns” Surprising how prevalent this attitude still is. It leads to large Centralized ops teams are
by snorkel 5y ago
“Innovation teams shouldn’t be burdened with operational concerns” Surprising how prevalent this attitude still is. It leads to large Centralized ops teams are inevitably going to be a bottleneck. If developers need to routinely create tickets with some other team to do get their work done then clearly the org is heading the wrong way. the org needs to invest in more self-service automation and ops training the developers with a mindset of reducing the size and responsibilities of their ops team rather than just hiring more ops which makes the problem worse.
- deleted 5y ago[deleted]
- cestith 5y agoSo you're agreeing with the author of the article on that point.
- snorkel 5y agoI’m not sure I agree because the advice from the article was mostly “grow the ops org” with a bit of push some ops responsibility back to dev teams, rather than seeing the ops org growth leads to further dependence on ops to get things done.