Construct a shared completion standard and integrated Increment
A hands-on PSM-I lab. You produce the real artefact and 10 automated checks verify it behaves the way the exam expects.
Try this labAll PSM-I practice
- Certification
- PSM-I
- Format
- Structured configuration
- Difficulty
- medium
- Estimated time
- 35 min
- Automated checks
- 10
The brief
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.
What the checks verify
Your work is graded on 10 independent properties, not on matching one reference answer.
- Standard, selected builds, bindings, evidence and flow/report rows are bounded and unique.
- One shared completion standard retains organizational/product minima and required flows.
- Actual selected builds form the required product groups and current change.
- Actual provider contracts form a complete acyclic integration.
- Component results match actual build, criterion, environment and passed status.
- Every applicable actual minimum and declared additional criterion is covered.
- Required product flows traverse actual compatible integrated components.
- Each exact integrated product flow has matching current evidence preserving I0.
- Integrated quality and regression closure support a usable current Increment.
- The report honestly reconciles retained baseline, verified parts, usable flows and uncovered work.
Where this sits in the PSM-I blueprint
- Domain
- Understanding and Applying the Scrum Framework
- Objective
- Artifacts and Commitments
- Skill
- Increment and Definition of Done
Part of PSM-I preparation
Labs are written by ExamNova to teach the decisions the exam tests. They are not reproductions of vendor lab content.