Leveraging Atlassian JIRA as our primary workflow tool provides a robust foundation for our service-offering processes to our clients.
As we want to streamline our operations by enabling us to handle and maintain more and more JIRA issues systematically, we want to ensure our processes align with the industry’s best practices and constantly evolve. This approach not only enhances our team’s productivity but also ensures we deliver a top-tier customer service to our clients.
This hierarchy is efficient because it allows for a high-level view of the project (via Epics), while also providing detail on what needs to be done at a granular level (via User Stories and Tasks). It also helps with prioritizing work, tracking progress, and managing changes.
BACKLOG
IN PROGRESS
IN REVIEW
DONE
EPIC
This is the highest level and represents a large body of work that can be broken down into smaller tasks. An Epic could be a feature, customer request, or business requirement. It’s usually something that will take several sprints to complete.
USER STORY
A User Story is a small, self-contained unit of work that can be completed in one sprint. It’s written from the perspective of the end user, outlining what they want to achieve, why it’s important, and what the desired outcome is.
TASK
Each User Story can be further divided into Tasks. Tasks are the smallest units of work and describe specific activities required to complete a User Story. They’re usually something that can be completed in a few days or less.