| Table of Contents |
|---|
What are tags?
In general tags are a way to categorise people and teams. They are highly customisable and can include things like could relate to many things such as skills, cost centre, funding source, leave type, etc.
Tags provide a visual flag and a way of discovering groups of people or teams “tagged” i.e. within a category. Against the person or team they can have
People and teams can be linked with multiple different tags against themwithout limitation.
There are also advance advanced use cases of tags that is allowed in TeamForm where it tags can be used to specify requirements during workforce planning, or be linked to comments and specification of membershipsother elements such as comments or membership specifications.
What are common use cases for tags?
Linking people with tags
Tags can be used for people to highlight their agile “hatted role” for example, a an “Agile Coach” tag. This is useful because an agile hatted role may be different from an individual’s official role or job title. Defining a list of “Specialist” tags allows or tags to capture these “Specialities” can allow an organisation to easily label these individuals so they can be found through search, or by visually identifying through use of a “badge” (see below).
...
Linking teams with tags
Tags can also be used for teams to group teams by things they have in common (where this information is them by a commonality not already included in a their work hierarchy), for example applications worked on, or team topology type . For example to highlight common tools or 3rd party applications they use to do their work, or their type in a given lexicon (e.g. “Enabling Team” in the lexicon from Team Topologies).
Other use cases
...
for tags
Advanced applications for Tags can be used in many more contexts, such as
Skills repository - bringing –bringing skills in as tags against each individual. See https://teamform.atlassian.net/wiki/x/EoCXo
Funding information - bringing –bringing in cost centres, funding source categories and any other information in as tags that so they can be attached to people and/or teams.
Resource Availability - to –to indicate who’s available by displaying who’s on what type of leave.
Etc.
For details on when tags should or shouldn’t be used, refer to When to use Tag vs People Attributes
What are the 3 different kinds of tags?
Simple Tags
There The 2 fundamental elements that make up a ‘tag’ in TeamForm . They are: Tags can simply contain a type and a value:
Tag Type - This is the –The broad category of what the tag is about or the purpose the tag serves.
E. egg.: identify agile rolesdissociate roles between “Agile” and “Traditional”, therefore the creating a tag type is then ‘Agile Role’as “Agile Role”.Tag Value - These are the values –The label that fit under the broad category umbrella of the tag type. eg
E.g.: Product Owner, Scrum Master, Transformation Leads
...
.
Each simple tag created is associated to a given type but represented as a single data point / tag value within each tag createdbased on its value. For example, Product Owner, Scrum Master and Transformation Leads are 3 separate tag values creating within the Agile Role tag type, hence represented as 3 separate individual tags within the same category of ‘Agile Role’ tag type.
...
Tags with Attributes
Within a An single tag value we can store additional data information which is often referred to as ‘tag attributes’ tag attributes.
For example within the ‘Cost Centre’ , given a Cost Centre tag type, we have cost centre ID 123456 as the tag value and we now want to nest additional information such as CAPEX or OPEX associated to cost centre ID 123456.
...
can store the name of the different cost centres of the organisation as individual values. Say Cyber Security, IT Support and Marketing. Now for each of these individual cost centre, we are allowed to store additional information as attributes. For instance: the technical Cost Center ID used in the budgeting system, its Funding Source, the name of the department it is Owned By and the Time Frame it is set for.
So for an individual tag associated to a specific value for this type:
Tag type: Cost Centre
Tag Value: Cyber Security
Tag Attribute - Cost Centre ID: 123456
Tag Attribute - Funding Source: OPEX
Tag Attribute - Owned By: CIO
Tag Attribute - Time Frame: FY2025
Attributes can be entered in as a simple text information, or can reference other existing people or team information within TeamForm also known as ‘entities’.
There are 2 types of attributes within TeamForm and each have it’s unique behaviour to tags:
Common attributes - Data stored within the tag value is applicable to multiple teams or people, hence changing one value of the attribute within the tag value will change it for all teams and/or people with the same tag value. For example, two people are tagged as ‘2025 Graduate’ and have the same “completion date” as of March 31st 2024. If I update the completion date to April 1st 2024, both people with the 2025 Graduate tag will now have an updated completion date.
Unique attributes - Data stored within the same common tag value is unique to the team and/or person with the tag which means changing one value of the attribute within the tag will not change for all teams and/or people with the same tag value. For example, two people can be tagged as “Departing” but have unique “departure dates” as attributes, where departure date is an unique tag for the Departing tag.
Tags with attributes in the tag name: Attributes can be configured to be included in the tag name. Multiple attributes can be concatenated together to form longer dynamic tag names.
...