QA Mob

QA mobs generally involve a large number of stakeholders. As a result, there can be a larger features list with a larger footprint and a resulting higher risk associated with deploys. With most organizations, the use of non-specialized tools is not consistent, resulting in a lack of ability to track and perform effective Postmortem analysis.

Benefits

QA mobs usually involve a large number of stakeholders, which can complicate communications during the event.

Standardized, streamlined, repeatable, and consistent process that can be templatized per team needs. The result is one source of truth to track all issues, remediation, and execution.

Expect larger feature sets, with a larger footprint, and hence higher risks associated with deploys.

Regardless of the size of the feature set, by creating a standardized, streamlined, repeatable, and consistent process that can be templatized per team needs, scaling does not become a limiting factor.

The use of the wrong tools to keep track and collaborate means the process is not repeatable and consistent results--exposing an inability to track and perform effective Postmortem reviews.

Increase in the team’s confidence, by reducing the QA Mob time and improving feature quality.