A comprehensive guide for every module
Every Scrumling module has a public guide that explains the subject properly: the problem behind it, how it works in practice, the mistakes that cost teams the most, and the questions worth asking before you commit. Read them without an account, download any of them as a PDF, and take the module when you want the scenarios and the assessment.
Scrum Master
Start here. Official Scrum theory, in plain language, before you jump into the simulations.
Read the guideWhat Scrum is, why it exists, and the mindset that powers it.
Read the guideServe the team. Remove impediments. Coach, don't command.
Read the guideScrum Master playbook for offshore, hybrid and time-zone-split teams.
Read the guideServe the team. Remove automated impediments. Coach delivery engineering, don't command.
Read the guideFacilitating retrospectives after failure, engaging silent teams, and coaching dominant seniors without breaking safety.
Read the guideCoach a mixed admin, developer, and architect team across seasonal releases, governor limits, and the Flow-versus-Apex fault line.
Read the guideHandle executive escalations, scope negotiation and budget conversations without collapsing the Sprint Goal or the team's focus.
Read the guideReplace velocity theatre with cycle time, work in progress, throughput and probabilistic forecasting that actually predicts a date.
Read the guideAdd a pull system, explicit policies and WIP limits to a Scrum team without abandoning Scrum.
Read the guideDrill the 2020 Scrum Guide rules a Scrum Master is assessed on, then sit a timed 80-question mock exam graded at the real 85 percent bar.
Read the guideProduct Owner
Play the value-maximizer. Order, focus, defend the Sprint.
Read the guidePlay the value-maximizer. Order, focus, defend the Sprint under AI-scale feature velocity.
Read the guideHow to hold Sprint Goals, fixed-scope contracts, and team autonomy under real pressure from VPs, clients, and CEOs.
Read the guideStop shipping confident guesses. Assumption mapping, small tests, continuous interviewing, and discovery that fits inside a delivery Sprint.
Read the guideTurn OKRs into outcomes a Scrum team can actually influence, not a quarterly wish list dressed up in a spreadsheet.
Read the guideDrill backlog ordering, value maximization and the Product Goal the way the assessment tests them, then sit a timed 80-question mock exam at the real 85 percent bar.
Read the guideDeveloper
Engineering trade-offs under sprint pressure: technical debt, Definition of Done, and shipping verified value instead of raw output.
Read the guideEngineering trade-offs when Copilot, Cursor, and PR bots meet TDD, the Definition of Done, and Sprint commitments.
Read the guideSlice long-running data work into real Sprint increments without pretending pipelines behave like features.
Read the guideRefine, estimate and slice work when the mental model is nodes and relationships, not rows and tables.
Read the guideRefine, estimate and slice work when your graph is in-memory, streaming, and expected to answer in milliseconds, not overnight.
Read the guideShip AI-assisted code fast without letting quality, review discipline or the Definition of Done collapse under the volume.
Read the guideEmbed security, GDPR and audit obligations into the Definition of Done, instead of bolting them on the week before release.
Read the guideTurn cloud, IaC and developer platform work into Sprint-shaped, product-owned Increments that other squads consume as a service.
Read the guideModernize a legacy monolith in thin, shippable Sprint slices, instead of a two-year waterfall rewrite that never lands.
Read the guideTurn feature flags, A/B tests and marketing telemetry into first-class Sprint content that connects code shipped to money moved.
Read the guideRun Scrum when part of the work is done by autonomous agents: who is accountable, what Done means, and why review becomes the constraint.
Read the guideFor QA Engineers, Testers and Developers: move from end-of-Sprint gatekeeper to a Developer accountable for quality from refinement onwards.
Read the guideEnterprise Agile
Own value on the Salesforce platform: configure, buy, or build, and defend the Sprint against release cycles and AppExchange drift.
Read the guideRun Scrum inside a ticket-heavy, SLA-driven ITIL org without pretending either framework does not exist.
Read the guideShip value on S/4HANA while keeping the standard system untouched, Sprint-friendly extensions, not waterfalled modifications.
Read the guideTurn AI regulation into ordinary Sprint work: risk tiers in refinement, obligations as acceptance criteria, and audit evidence as a by-product of delivery.
Read the guideRun the day-to-day governance of AI features inside normal Sprint work: approvals, policy, supply chain, evals and incident response.
Read the guideChoose honestly between SAFe, LeSS and Nexus, and descale first wherever you actually can.
Read the guideLearn Scrum by playing, not by reading slides.
Every role, every event, every artifact, practiced under pressure in the browser. Free forever, certificate on completion.
Start the free course