A bug bash is a team event where teammates rigorously test and identify bugs in a product, often at the end of the System Development Life Cycle before a feature ships to users. Bug bashes are beneficial as they help teams identify many bugs and improvements in a short time-span, provide an opportunity for cross-functional teams to work together, and get everyone more familiar with the user experience and aligned on ways to improve it. To run a successful bug bash, teams should decide who to include and give everyone a role, schedule the event and define its scope, establish a bug reporting process, and run the event following three stages: introduction, bug hunting, and reflection. Best practices for running a bug bash include limiting the scope of what will be tested and commented on, creating a welcoming environment, and helping people create actionable bug reports.