From this link I assert that a feature is a set of backlog items, but what is an epic supposed to be?
An Epic is a Backlog Item that contains at least one Story, even if the Story is just an investigatory one. Usually, a functional Epic contains analysis Stories that produce functional Stories that also belong to the Epic.
Epics can be broken down into specific pieces of work, called Features. These are based on the needs and requests of customers or end users and is sized or split as necessary to be delivered by the Agile teams. Epics are a helpful way to organise your work and to create a hierarchy.
Epics are an important practice for agile and DevOps teams. When adopting agile and DevOps, an epic serves to manage tasks. It's a defined body of work that is segmented into specific tasks (called “stories,” or “user stories”) based on the needs/requests of customers or end-users.
Issues and Tasks are used to track work, while Epics are used to group work under larger scenarios. The Basic process is available with Azure DevOps Server 2019 Update 1 and later versions. To learn more about using these work item types, see Plan and track work.
The general consensus is that:
Theme is generally implemented as a tag in TFS and VSTS.
This is a practice that is in line with Scrum Framework, Nexus Framework, and SAfE methodology.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With