## Are Specific Terms Required for Decomposition Levels? No, the terms and levels can be adapted to fit the team’s context. For example, some teams may only use two levels, such as Epic and PBI, instead of three. In many cases, the naming conventions for backlog levels are influenced by the project management tool in use. For example, Azure DevOps typically follows the hierarchy of Epic → Feature → Story, while Jira often uses Initiative → Epic → Story. ## Works Consulted 1. [Jira Issue Type Hierarchy: Everything You Need to Know](https://www.devsamurai.com/en/jira-issue-type-hierarchy/) | DevsSmurai.com | Accessed 13 Jul. 2025. 2. [Define features and epics to organize your backlog](https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/define-features-epics?view=azure-devops&tabs=agile-process) | Microsoft.com | Accessed 13 Jul. 2025. ## Connections follows:: [[1.1b1b1 Decomposition Adds Value Only When It Adds Clarity]] topics:: [[Epic]], [[Feature]], [[Story]], [[Levels of Decomposition]], [[Backlog Refinement]] ![[Footer]]