Problem
Jira is the acknowledged market leader among project management tools and is a great tool for managing tasks, their requirements, and life cycle. In a regular Jira workflow, project manager’s tool set for ensuring speed and quality of the delivery are limited to task description (i.e well-designed input, requirements, and quality criteria), as well as intelligent assignments.
...
Maintaining the kind of knowledge needed to make efficient and unbiased assignments, leveraging team potential efficiently becomes a significant challenge under the conditions of rapid growth, fast-paced projects, and evolving technologies .
Solution
Adding “skills” as an abstraction between your tasks and your workers allows you to significantly simplify management for both:
Project managers gain the missing piece of the puzzle to, enabling them to guarantee quality of the delivery through a single mechanism of task definition, embedding worker requirements into the task along with the implementation requirements and quality criteria.
Team managers gain visibility into current, future, or past demand for their team members skills. Knowledge scarcity/density and bottlenecks become visible, facilitating measures like training, hiring, talent distribution between teams.
How it works
“Skills for Jira” adds a new custom field type - “Skillset”. These fields match the specified skill requirements with users, exposing this mapping for you to query via JQL or use in workflow conditions.
“Skillset” can become merely a convenience helper (show me who has the skills/knowledge so that I can make a better assignment decision) or an enabler for fully automated assignments (e.g. people get their personal work queue in the form of a JQL filter, can pull their next assignment from the ones that match their expertise, and are restricted from pulling tasks they don’t have expertise in).
...
.
What benefits do skill-based assignments provide?
...
| Info |
|---|
Knowledge map and documentation are especially relevant for large/old projects or for projects that are considered for acquisition. |
How it works
“Skills for Jira” adds a new custom field type - “Skillset”. These fields match the specified skill requirements with users, exposing this mapping for you to query via JQL or use in workflow conditions.
“Skillset” can become merely a convenience helper (show me who has the skills/knowledge so that I can make a better assignment decision) or an enabler for fully automated assignments (e.g. people get their personal work queue in the form of a JQL filter, can pull their next assignment from the ones that match their expertise, and are restricted from pulling tasks they don’t have expertise in).
| Info |
|---|
“Skills for Jira” is intentionally unopinionated about work assignment process. Rather than enforcing a particular process, we offer you a “Skillset” field, adding another powerful tool in your toolset. You can use it in modeling your work assignment process as you see fit. |