Free Scrum course. Learn by playing, not by watching slides.
A modern, gamified course that takes you from the empirical foundations of Scrum through every event, artifact, and accountability, and drops you into role simulations where the tradeoffs are real.
How Scrum Is Your Team?
You know Scrum. But how well does your team actually use it?
Designed for Scrum teams. Built around real workplace situations. Free while we pilot Scrumling with teams in Burgas.
Concise, opinionated lessons, no fluff, no jargon dumps.
Interactive labs where you play PO, SM, and Developer under pressure.
Every module ends with a short quiz: pass it and earn that module's certificate.
Everything you need. Nothing you don't.
Brand New to Scrum & Considering Certification?
New to Scrum, or getting ready to sit PSM I or PSPO I? Start with the beginner primer for the fundamentals, or go straight to the Certification Prep Hub for timed mock exams.
Start here. Official Scrum theory, in plain language, before you jump into the simulations.
What Scrum is, why it exists, and the mindset that powers it.
Play the value-maximizer. Order, focus, defend the Sprint.
Serve the team. Remove impediments. Coach, don't command.
Engineering trade-offs under sprint pressure: technical debt, Definition of Done, and shipping verified value instead of raw output.
Scrum Master playbook for offshore, hybrid and time-zone-split teams.
Play the value-maximizer. Order, focus, defend the Sprint under AI-scale feature velocity.
Serve the team. Remove automated impediments. Coach delivery engineering, don't command.
Engineering trade-offs when Copilot, Cursor, and PR bots meet TDD, the Definition of Done, and Sprint commitments.
Facilitating retrospectives after failure, engaging silent teams, and coaching dominant seniors without breaking safety.
How to hold Sprint Goals, fixed-scope contracts, and team autonomy under real pressure from VPs, clients, and CEOs.
Own value on the Salesforce platform: configure, buy, or build, and defend the Sprint against release cycles and AppExchange drift.
Coach a mixed admin, developer, and architect team across seasonal releases, governor limits, and the Flow-versus-Apex fault line.
Run Scrum inside a ticket-heavy, SLA-driven ITIL org without pretending either framework does not exist.
Slice long-running data work into real Sprint increments without pretending pipelines behave like features.
Refine, estimate and slice work when the mental model is nodes and relationships, not rows and tables.
Refine, estimate and slice work when your graph is in-memory, streaming, and expected to answer in milliseconds, not overnight.
Ship value on S/4HANA while keeping the standard system untouched, Sprint-friendly extensions, not waterfalled modifications.
Ship AI-assisted code fast without letting quality, review discipline or the Definition of Done collapse under the volume.
Embed security, GDPR and audit obligations into the Definition of Done, instead of bolting them on the week before release.
Turn cloud, IaC and developer platform work into Sprint-shaped, product-owned Increments that other squads consume as a service.
Handle executive escalations, scope negotiation and budget conversations without collapsing the Sprint Goal or the team's focus.
Modernize a legacy monolith in thin, shippable Sprint slices, instead of a two-year waterfall rewrite that never lands.
Turn feature flags, A/B tests and marketing telemetry into first-class Sprint content that connects code shipped to money moved.
Run Scrum when part of the work is done by autonomous agents: who is accountable, what Done means, and why review becomes the constraint.
Stop shipping confident guesses. Assumption mapping, small tests, continuous interviewing, and discovery that fits inside a delivery Sprint.
Turn AI regulation into ordinary Sprint work: risk tiers in refinement, obligations as acceptance criteria, and audit evidence as a by-product of delivery.
Replace velocity theatre with cycle time, work in progress, throughput and probabilistic forecasting that actually predicts a date.
Turn OKRs into outcomes a Scrum team can actually influence, not a quarterly wish list dressed up in a spreadsheet.
Run the day-to-day governance of AI features inside normal Sprint work: approvals, policy, supply chain, evals and incident response.
Add a pull system, explicit policies and WIP limits to a Scrum team without abandoning Scrum.
Choose honestly between SAFe, LeSS and Nexus, and descale first wherever you actually can.
For QA Engineers, Testers and Developers: move from end-of-Sprint gatekeeper to a Developer accountable for quality from refinement onwards.