Ownership in a DevOps and InnerSource environment
summary
BBC TV apps (iPlayer and Sounds) split responsibility across five cross-discipline teams, owning product areas like account, browse, playback UI plus an app core and specialized media playback and build/launch teams supporting 11 million weekly users. Ownership covers full DevOps lifecycle and uses GitHub code owners for notifications. Roles are maintainers, trusted committers and contributors; current gap is trusted committers outside owning teams. Experimentation includes distributed ownership for app core with at least one maintainer per consuming team.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 1:50Understanding ownership in software
- 3:40Ownership structure at BBC
- 6:27DevOps and ownership lifecycle
- 7:09Ownership principles and team missions
- 9:39Hard vs soft ownership models
- 11:49Maintainers and trusted committers
- 13:56Distributed ownership approach
- 15:21Summary and key takeaways
related talks
42mWho Owns This Code? Navigating Code Ownership from Inner to Open Source
11mChanging Ops And Dev Culture At The BBC
47mThe Challenges of Public Code: Building an Open Source Culture at BBC
16mContinuous Delivery and InnerSource - Why you Should be Doing Both
21mTeam Ownership - Who Owns Production
39mMicroservices and Continuous Delivery at the BBC
26mTen (Hard-Won) Lessons of the DevOps Transition
30mHow Go Helped Accelerate Software Delivery at the BBC