Are you saying, that every team needs to run its own source control repository, its own copy of CI…
Sceptical Meerkat
1

No, but it becomes a fine line. Eg I wouldn’t expect a scrum team to have to change anything about the source control during the sprint. I’d expect this infra to be managed by another team. But what about build environments? You don’t want each scrum team managing their own, but it can become a tragedy of the commons — if the scrum team is blocked because of a lack of suitable build machines then this is a problem.

I can imagine a scenario where there are operations folk within the scrum team who can admin this kind of shared infrastructure, but it obviously has to be synced across the organisation. As soon as you have anything shared the split between silo vs scrum team is much less clear.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.