Requirements, User Stories and Traceability in SAP Cloud ALM

Keep this: job aid

Requirement traceability checklist for SAP Cloud ALM

• Create each requirement from its solution process; add workstream, priority, tags and acceptance criteria.
• Capture process knowledge as notes, not requirements.
• Approve or reject every requirement before the scope gate; record the reason for rejections.
• Refine approved requirements into user stories; use project tasks only for organizational work.
• Give every requirement one feature (leading practice) and assign its stories to it.
• Write requirement-level acceptance tests from the workshop criteria, with boundary values.
• Weekly: filter Requirement Traceability for orphans, untraced stories and built-not-tested items.
• At each gate: report design, execution and pass coverage per process, plus unbuilt requirements.
• Give every gap a decision (fix, condition, defer, reject) with an owner and a date.