Bug Blitz

A time-boxed, team-wide testing event where people from across the organisation are invited to explore a product together and report issues they find. Unlike structured regression testing, a bug blitz is open-ended and relies on the diversity of participants (developers, designers, support staff, marketers) to surface defects and usability problems that a small QA team might miss. For example: inviting the whole company to spend an afternoon clicking through a new feature before it ships; or running a focused blitz on a specific area of the product after a major refactor.