Azure DevOp - Managing Requirements

Great questions, and the mapping does feel odd if you're coming from DOORS or Requisite Pro. Native ADO work items are built for scheduling work, so a requirement tends to behave like a backlog item that gets "done". What helps is treating requirements as versioned artifacts that live alongside the sprint backlog rather than inside it: use User Stories or Requirement work items for the content, keep acceptance criteria on them, and baseline the set when it's approved so later changes are tracked against a known state. For regulated work, the piece that matters most is traceability from requirement to design, test case, bug and risk, with a matrix you can produce for audits. We cover how that works on ADO here: https://www.modernrequirements.com/products/modern-requirements4devops-features/traceability/ (disclosure: I work at Modern Requirements). Happy to go into reuse across similar products if useful.