# Understand drift patterns

Variance compares commits and PRs to the approved requirement and plan—flagging discrepancies fast in Slack, Jira, and GitHub.

## What it does

Turn delivery uncertainty into predictable outcomes with intelligent variance tracking.

- Continuously compares commits and PRs against the approved requirement, impact map, tasks, and acceptance criteria.
- Detects drift - files changed outside the impact map, PRs that don't satisfy the acceptance criteria, or tasks implemented out of sequence.
- Posts actionable alerts to Slack and Jira with a concise diff summary, affected areas, and suggested next steps.
- Auto‑creates follow‑up Jira tickets linked to the PR for remediation or re‑scoping.
- Generates a periodic variance report by requirement/epic/sprint with configurable ignore rules and thresholds.

## How it helps

Maintain delivery confidence with automated drift detection and governance.

### Reduces rework by catching scope creep and mismatches before they land in main.
### Protects velocity with fewer mid‑sprint surprises and more predictable delivery.
### Improves quality by enforcing AC adherence and keeping tests aligned with intent.
### Increases accountability with a clear, auditable trail of plan‑vs‑build decisions.
### Enables lightweight governance so leaders set guardrails without micromanaging.
### Match Implementation plan with execution – highlight deviations.

## Frequently Asked Questions

Everything you need to know about variance analysis.

### What does Variance actually check?
### Will this spam us with alerts?
### What's required to enable it?

Need help understanding your variance patterns? Our analytics experts are here to help at [support@brewstudio.in](mailto:support@brewstudio.in)