signal busAll systems operationalScrums.com x Vercel for AI engineering ↗
summaryManual certification of a defined release — agreed acceptance criteria, reproducible defects with severity, and a go/no-go readiness report.🔒 Sign in for pricing·★ 5.0·● available now·vetted by Scrums.com

delivery · CAT-30030792 · rev 1.0

Manual QA Release Certification. @qa-release-certification

Deliverydelivery · outcome-driven-sprints · qa · testingScrums.com● available now
5.0Reviews ▾

Rated 5.0 / 5 by clients on GoodFirms.

Read verified reviews on GoodFirms

Vetted by Scrums.com Platform

Provider Scrums.com

Last review 2026-08-14

01

What you get

the numbers that matter
Ready in

≈ 2 weeks

signed to first PR

Retention

96%

engagements renewed

Match

96%

to your stack & domain

Test a defined release against agreed acceptance criteria and deliver a release-readiness report with reproducible defects and severities.

02

How this operator works

every way of working, already decided
A · capability focus

Owns the system, not the ticket

Takes end-to-end ownership of a service or surface. Design, delivery, on-call. And is measured on outcomes, not hours.

B · ways of working

Embedded, async-first, instrumented

Works inside your repos, your CI and your rituals. Daily written standups, decisions logged. No status-meeting tax.

C · reliability posture

Runbooks, canaries, reversible deploys

Every change gated and reversible. Incidents get a timeline and a postmortem; nothing ships without a rollback.

D · comms & cadence

Plugged into your Slack & rituals

Joins standups and retros, reports weekly against the goal. You get an operator, not a queue.

E · tooling

Brings a pre-wired stack or adopts yours

Infrastructure and observability as code by default. No bespoke setup tax to absorb.

F · onboarding

Scoped, gated, reversible

Week-1 shadow, week-2 ownership, swap on request inside the trial window. No long-tail handover risk.

·

Overview

Some releases need a human to try to break them before customers do. This sprint tests a defined release candidate against agreed acceptance criteria — functional flows, edge cases, and exploratory charters — executed by QA engineers who document everything they find.

Every defect is reproducible: steps, environment, evidence, and severity, triaged against the criteria you signed off. Scrums.com QA teams have run this discipline across 1,200+ projects. The finish state: a release-readiness report with a clear go/no-go recommendation and a ranked defect list your team can act on.

·

What's included

Acceptance criteria & test charter

Criteria agreed up front — or drafted from your requirements — plus exploratory charters for the areas most likely to hide problems.

Structured manual execution

QA engineers execute the functional flows, edge cases, and charters methodically, on the environments and configurations that matter.

Defect reporting

Every defect reproducible: steps, environment, evidence, and severity, triaged against the criteria you signed off.

Release-readiness verdict

A clear go/no-go recommendation with the ranked defect list behind it — a document your release meeting can act on.

·

How it works

  1. Scope. Agree the acceptance criteria, environments, and test charter.
  2. Build. Execute structured and exploratory testing; log reproducible defects with severity.
  3. Handover. Release-readiness report, go/no-go recommendation, and a defect walkthrough.
·

Part of every Delivery Plan

The Manual QA Release Certification is a menu item on the Scrums.com delivery catalog, available at every plan tier. Add it to your plan backlog and your delivery team schedules it like any other item — scoped, tracked, and reported through the SEOP. See Delivery Plan Tiers.

·

FAQs

Do you fix the defects you find?

No — certification and remediation stay separate so the verdict stays honest. Fixes go to your team or get scheduled as their own menu items, and re-certification of the fixed build can follow.

What do we need to provide?

A testable build and environment, test accounts and data, and acceptance criteria — or requirements the sprint can draft criteria from.

We release too often to certify manually every time. What then?

Certify the high-stakes releases and automate the rest: the Web Test Automation Suite item builds the recurring coverage, and Managed QA-as-a-Service carries testing as an ongoing function.

03

What's included

in every engagement · no add-ons
Acceptance criteria & test charterincl.
Structured manual executionincl.
Defect reportingincl.
Release-readiness verdictincl.
04

Track record

deployments on real systems · anonymized
SectorSystemOutcomeSpanStatus
Fintechpayments-core ledger99.97% achieved14 mo● complete
Commercecheckout platform−38% incident rate9 mo● complete
Health SaaSdata plane0 SEV1 in 6 mo11 mo● active
Logisticsrouting enginezero-downtime cutover7 mo● complete
AI infrainference clusterp99 −120 ms5 mo● active
05

Works inside your stack

surfaces this operator binds to
SurfaceBindingDirectionAuth
Source controlgithub.com/<org>reviews + writesOIDC
CI / CDscm-flow · deploy-servicegates deploysOIDC
Observabilityotlp://collector:4317metrics + alertsmTLS
Commsslack://<workspace>standups, incidentsSSO
Secretsvault://scrums/op/<id>short-lived credsSPIFFE
On-callpagerduty://<org>primary / secondaryAPI token
06

Boundaries

what to deploy instead

Scoped to this discipline. For an adjacent capability, compose a second operator into the squad. compose →

Not a fractional advisory engagement. For advisory-only, contact platform@scrums.com.

07

Deployments

the only social proof we publish

402deploys

across 38 organizations

+24 last 30 days · median age 11.4 mo · retention 96%

08

Pricing

one number · one footnote
billed monthly

🔒 Sign in for pricing

Available at all Delivery Plan Tiers →

All-in: the operator, delivery manager and replacement guarantee. No recruiter fee, no markup surprises.

Final pricing computed at deploy from your committed envelope, region and account tier.

·

FAQ

common questions
How is Manual QA Release Certification priced?

Pricing is shown to signed-in accounts. Sign in to view the rate; pricing is computed from your engagement scope, region and account tier.

Is Manual QA Release Certification available now?

Yes. It is published and deployable directly from the Scrums.com catalog.

Can a Manual QA Release Certification deployment be reversed?

Yes. Deployments are reversible with a one-click swap inside the trial window.

Who provides Manual QA Release Certification?

Scrums.com, vetted by the Scrums.com platform.

·

How it compares

vs other delivery
OptionFromStackStatus
Manual QA Release Certification · this one🔒 Sign in for pricingdelivery · outcome-driven-sprints · qa● available
Release Backlog Burn-Down Sprint🔒 Sign in for pricingdelivery · outcome-driven-sprints · backlog● available
Technical Debt Reduction Sprint🔒 Sign in for pricingdelivery · outcome-driven-sprints · technical-debt● available
Critical Application Rescue🔒 Sign in for pricingdelivery · outcome-driven-sprints · rescue● available
09

Commonly deployed with

more delivery

More delivery

Release Backlog Burn-Down Sprint

Deliver a prioritized set of small production-ready changes that have accumulated behind a constrained delivery team.

All plan tiersoutcome-driven-sprintsbacklogdelivery-capacity
See options →

Technical Debt Reduction Sprint

Remove a defined cluster of high-cost technical debt tied to reliability, speed, maintainability, or developer friction.

All plan tiersoutcome-driven-sprintstechnical-debtrefactoring
See options →

Critical Application Rescue

Stabilize a failing, broken, or abandoned application, restore reliable operation, and create a prioritized path forward.

All plan tiersoutcome-driven-sprintsrescuestabilization
See options →
billed monthly

🔒 Sign in for pricing