Software is full of surprises. No matter how careful you are when writing code, it can behave differently than you intended. Exploratory testing mitigates those risks. Exploring is especially important to detect unexpected side effects on large, complex systems where it simply is not possible to reason through all the implications of a given change nor can automated tests cover all the interesting permutations. This session explains in detail how we use exploratory testing on Cloud Foundry at Pivotal. We have dedicated explorers who rotate through development teams, but everyone on the team explores. Programmers pair with explorers on executing charters, and explorers pair with programmers on feature delivery. We use charters to organize our exploratory efforts; PMs prioritize those charters in backlogs along with other stories. Along the way we’ll contrast the way we explore on Cloud Foundry with other styles of integrating exploratory testing into an Agile team.