Add Your Heading Text Here
Funktion
In Azure DevOps, a feature is a mid-level work item that represents a distinct capability a product delivers, sitting below an epic and above user stories. A feature groups the stories that together provide something useful to users, making it the level where a shippable piece of value takes shape.
What it means
A feature is the bridge between a broad epic and the small, buildable user stories beneath it. It is concrete enough to describe a real capability, like 'guest checkout' or 'export to PDF', but still large enough to need several stories to complete. Teams use features to plan releases, since a feature usually maps to something they can ship and talk about.
For requirements, features are a natural grouping level. A set of related requirements often belongs to one feature, and tracing them up to that feature shows how individual details serve a coherent capability. Keeping features appropriately sized, neither as sprawling as an epic nor as small as a single story, is what keeps the backlog readable.
In practice
Within a 'saved payment methods' epic, a team defines a feature called 'add a card during checkout'. That feature holds user stories for entering card details, validating them, and confirming the save. The feature is the unit the team plans a release around, while the stories are what they build sprint by sprint.
Häufig gestellte Fragen
What is the difference between a feature and a user story?
How does a feature fit into the Azure DevOps hierarchy?
Manage requirements the modern way
Modern Requirements brings documentation, traceability, and reviews together inside Azure DevOps.
