Forum Discussion
Azure DevOp - Managing Requirements
We are looking at how to document and manage requirements within Azure DevOps. Sample documentation is here: https://learn.microsoft.com/en-us/azure/devops/cross-service/manage-requirements?view=a...
I see 811 views, but no replies. I have the same question. Does each requirement have its own User Story? Do we just ignore the User Story and Acceptance criteria for that user story since it's actually a requirement that we're documenting? Never assign the user stories to a sprint? No story points? It seem klugey. If I use tasks for each individual requirement, do I just assign them to an "epic" which is the product or feature that the requirements are for?