What are tags good for?
Tagging is a powerful and versatile method to manage different aspects of your projects. You can organize tags into categories to use tags as flexible parameters of your user stories. You can filter your backlog or board based on tags to focus on user stories with the specific characteristics.
For example, if you’re using Scrum Mate to manage agile software development, you can use the following tags and categories.
- User personas. You can define different types of users who will use your product. For example, if you develop a product for retailers, you will have different features for different personas. A store manager will need something else compared to a cashier or a customer. You can use tags to indicate which user groups will benefit from a given story.
- Target versions. You can use tags to define target versions of the product, the given user story will be introduced.
- Issue types. A traditional approach to software development requires you to define the type of issue that the user story addresses. For example, it can be a defect, an improvement, or a new feature.
- Risk categories. One of the important aspects of prioritization is the risk of a user story. For example, you can create the following tags to indicate risk: ‘High risk’, ‘Medium risk’, ‘Low risk’,
- Story readiness. Product owners can use tags to indicate the readiness of a user story for development. A tag called ‘Sprint ready’ can indicate that the user story is clearly defined, so the team can start implementing it. The tag ‘To be discussed’ might indicate the product owner wants to discuss the idea with the development team.
Tags provide with an almost unlimited flexibility for agile teams in prioritizing and tracking user stories.
Using colored tags
You can make a tag colored to highlight them. For example, a tag called ‘Bug’ can be colored to red to make it more conspicuous on a backlog item or card on the board.