Credentials

AI Sprints Practitioner credentials

Practitioners earn the AI Sprints Practitioner credential through hands-on coaching. It recognizes competence to direct AI, confidence to use it, and the ability to explain and vouch for the result — shown in artifacts and application in daily work.

Three credentials — Developer, QA and Product Owner — for one practice across the delivery team. Issued through BadgeCert.

The three credentials

One practice, three roles

AI Sprints Practitioner credential badge, Developer (DEV) Developer · DEV

AI Sprints Practitioner — Developer

For developers who direct AI agents on delivery work and stand behind what ships.

The practiceThe AI Sprints developer practice, applied hands-on: intent made explicit before the agent runs, and every change reviewed, tested and explainable.
Issued through BadgeCert
AI Sprints Practitioner credential badge, Quality Assurance (QA) Quality Assurance · QA

AI Sprints Practitioner — QA

For QA engineers who direct and verify AI-assisted testing, with human judgment in control of quality.

The practiceThe AI Sprints QA practice, applied hands-on: AI does the scaffolding, people own the judgment, and quality keeps pace with AI volume.
Issued through BadgeCert
AI Sprints Practitioner credential badge, Product Owner (PO) Product Ownership · PO

AI Sprints Practitioner — Product Owner

For product owners who make intent explicit for AI-enabled teams.

The practiceThe AI Sprints product owner practice, applied hands-on: specs and acceptance clear enough that developers, QA and their AI agents build from the same intent.
Issued through BadgeCert
How it is earned

Practiced hands-on, not in a classroom

Goals › Learn › Practice › Present › Evaluate › Feedback › Coach › Reflect

Hands-on, on real work

Practitioners practice on sprint-like projects, with personalized feedback, evaluation and ongoing coaching. They also practice presenting their work, sharing standardized metrics, and exercising human judgment.

Tracked afterward

The credential rests on artifacts and application in daily work — speed and quality together, measured against the team's own baseline.

One practice across the team

Developers, QA engineers and product owners can practice in parallel from shared specs. The practice is written down and shared, so it lives across the team, not in two people.

Coaching with an exit

Credentialed practitioners and champions keep the capability in-house when we leave; champions progress to the AI Sprints Champion credential. Tool- and LLM-agnostic: the practice is the asset; the tools change every few months.

Want to verify a credential or ask about one? Send us a message.

Bring your team to Practitioner.

A 45-minute benchmarking and planning call. You leave with a baseline we can measure against, an ROI target set before any spend, and the shape of a first cohort — roles, format, dates.