Abstract: Extreme Programming (XP) provides a set of technically rigorous, team-oriented practices -- e.g. Test Driven Development, Continuous Integration, and Pairing -- that empower teams to deliver high quality software, iteratively. At Pivotal, our Labs practice built their reputation on their particular flavor of XP. However Pivotal is more than Labs: we ship enterprise products including Pivotal Cloud Foundry, Greenplum Database, and GemFire. How does XP apply when you have multiple teams collaborating across multiple timezones and locations to deliver a shipping product? This talk lays out the XP practices as the foundation but then explains how we operate at scale to achieve visibility, tight feedback loops, and radical collaboration even with large products and distributed teams. This talk covers what we've learned about organizing CI pipelines, the way we think about organizing teams around code ownership, and how we deal with cross-team dependencies. The answers we have found are simple, but as we all know simple can be very, very hard. In addition to looking at our practices, this talk will consider the cultural elements that enable us to succeed at applying XP at scale.
Learning Outcomes: - * How to create visibility and awareness between teams even when they are geographically distributed
- * Ways to increase collaboration and deal with blockers due to cross-team dependencies
- * Ways to think about code ownership across teams
- * How to avoid the "tragedy of the commons" in CI when multiple teams commit to the same repo
Attachments:
