PSM-I · Foundational

Professional Scrum Master I

Apply Scrum accountabilities, empiricism and product delivery decisions in realistic team situations.

Start Free

Your free account includes a full PSM-I practice exam.

ExamNova practice

Your first session

Questions: 80
Time limit: 60 min
Coverage: 3 domains

Practise, review your answers and see where to focus next.

Is PSM-I your next step?

Explore the coverage below to see how this certification fits your study goals.

What you’ll study

Your PSM-I practice covers every domain on the exam.

Understanding and Applying the Scrum Framework
Developing People and Teams
Managing Products with Agility

Consult the official guide for the vendor’s current exam outline.

Put it into practice.

Explore hands-on tasks connected to PSM-I. These are real Labs from the catalogue.

Lab

Order an evidence-gated backlog with distinct value trade-offs

Repair learning-backlog.json. goal:{id,focus} preserves complete-paid-order and accessibility or usage-learning. order:[{item,batch,effort}] selects actual source candidates once, chronologically, with immutable effort and every prerequisite in an earlier position and earlier batch. Each chosen delivery item uses the selected route. Combine actual source effort in capacity1=4,2=5,3=5; understated printed effort cannot create capacity. decision:{route,batch,evidenceRef,basis,recommendTo} selects native/N0 or hosted/H0 after supported corresponding discovery and no later than build/config. Use a source-supported basis, retain maximum recurring cost3 and recommendTo po. Both routes and optional extra research or promotion can be defensible when real constraints hold. dispositions:[{item,status,reasonRef}] accounts for all nine source candidates: planned iff ordered, otherwise deferred, with exact relevant kind reasons from the briefing. inspection:{afterBatch,evidenceRefs:[IDs],action,claim} inspects supported chosen-route learning afterBatch1; optional other supported findings may join it. Use reorder-from-learning and conditional-backlog-plan; no artifact creates approval. report:{goalForecastBatch,focusForecastBatch,totalEffort,learningEffort,deferredEffort,recurringCost,cycleLoad:[{batch,effort}]}. Goal finish needs actual supported chosen verification. Focus integration follows chosen build/config; focus finish is max(core,focus), otherwise null. Unsupported/overloaded or wrongly understated prerequisite work cannot support either outcome. Reconcile all source effort, learning investment, deferred opportunity, recurring cost and three batch loads. Scope order affects consequences; same-batch independent rows and disposition/load rows may be reordered. Save progress, inspect failures and repair without Reset.

hard · About 40 min

Lab

Construct a shared completion standard and integrated Increment

Repair increment-manifest.json. Construct standard:{quality:[criterion IDs],flows:[flow IDs]} with organizational/product minima; extra criteria are permitted if fully covered. manifest:[build IDs] must include a2, one api/web/mail build and no repeated group. bindings:[{consumer,contract,provider}] must provide every selected build's required contract exactly once from another selected build that exports it. Omit extra bindings; actual integration must be acyclic and closed. verification:[{build,criterion,evidenceRef}] must cover each applicable required criterion for every selected build, using a passed result for that exact build/criterion in integration-26. Irrelevant, failed, previous-version or development results provide no current coverage. Omitting a minimum from standard cannot waive actual demand. flowTraces:[{id,path:[build IDs],evidenceRef}] must cover each required flow once. A path starts with its entry kind, ends at an api build with no remaining requirement, and follows actual consumer→provider bindings through selected integrated builds. Its result must pass for the exact ordered path, integration-26 and baseline I0. report:{baseline,verifiedBuilds:[IDs],usableFlows:[IDs],uncovered:[IDs],incrementUsable:boolean}. A build is verified only when all its applicable quality requirements have valid evidence. A flow is usable only with a valid path and regression result and all path builds verified. uncovered lists build:criterion gaps and flow:id for required unusable flows. incrementUsable requires the shared minima, coherent manifest, closed bindings, valid complete quality and all declared required flows. Report retained I0 and actual derived facts even during partial repair. Bridge and coordinated upgrade routes are both feasible; a stronger performance standard has different evidence consequences. Preserve the prior Increment and quality. Save and repair incrementally without Reset; this is evidence analysis, not executed delivery.

medium · About 35 min

Make PSM-I your next step.

Create your free account. Start practising.

Start Free