...
- Determine your requirements with respect to a usable list/taxonomy of skills
option 1: create a new custom field of type "Skill" per specified skill as Jira administrator and assign suitable screens
- Determine a set of suitable profiles each having a set of skills including their minimum characteristics
option 2: create a suitable set of profiles. Each profile consists of a set of skills, already existing and re-used or new additional skills (alternative to the creation of skill-custom fields (see above), you can do that as part of creation of profiles)
- Each user has got the option to fill out her/his own current skill characteristic within their user profile (skills & profiles)
On your personal page of "Skills & Proficiencies", each user can maintain her/his skills and level of proficiency as percentage on tab "my Skills":
On next tab "my Profiles", each user may compare own skill set with defined reference profiles or select option "automatic determining best fitting profile" for automatic matching:
Resulting e.g. in a skills-radar like the following one after commit via "apply" button at the bottom of the page:
Finally: on tab "my Personality Type", each user can excercize a personality test by answering a couple of questions (just click on answer A or B, which fits as best for the user)
Based on that questionary, one of sixteen different personality types will be determined matching as best: the radar axis' display all eight psychology measurements and a larger textual interpretation help to understand better. For all personality types, that interpretation is structured as follows:
a) Portrait of the personality type
b) Jungian functional preference ordering
c) Relationships
d) Strengths
e) Weaknesses
f) What does Success mean to that personality
g) Potential Problem Areas
h) Explanation of Problems
i) Solutions
j) Living Happily in our World as an xyz
k) Specific suggestions
l) Ten Rules to Live By to Achieve Success
- Specify the necessary skills and their minimum characteristics per issue
If the necessary skills are not displayed for your issue, please ask your jira-administrator to assign the existing skills to the related edit-screen and/or create the missing skills (see topic #1, above)
- Assign by skill: automatically get proposals of best matching users based on the required skills and maintained/available user skills
Click on the link "assign by skill" and you will see a to get a sorted list of all employees configured as " assignable users" of the project on which the process is based, divided into employees with granted data sharing and without them. Employees who have been released are sorted automatically. A "best match" procedure algorithm is used as a for sorting criterion with regard to the minimum requirements of the relevant transactionrequired skills and proficiencies. The top 5 of this list are visualized graphically on the skill radar by default. By un/selecting the checkbox in front of each employee user you can adjust this as you wish and : the skills radar updates itself will update automatically. In addition to the degree of coverage of the skills and their aggregated total number, the personality type is also displayed if this was previously determined by the employee during the integrated test. With related user by testing. Having the same technical skills, this serves to make decisions a decision between different users with regard to the their typical personality/character of the employees (not everyone is in ideal hands in every project environment: with . With optimized staffing, the resulting team performance is significantly better and usually leads to fewer frictional losses).
Optionally, you can also search for employees: click into the input text field and simply enter acombination of characters or a more complex regular expression (for example if the correct spelling of a name is unknown). Not only the displayed names are searched but also the email addresses for better finding. By clicking on a team member/user within the lists on the left or directly on the polygon of skills on the right, that user is selected and automatically assigned to that issue if you commit via the "Assign" button on the bottom.
What does column "coverage" mean?
Per axis on the radar diagram, the minimum requirement with regard to skill and level of proficiency (in percent) is compared the the user's one. If the user's skill has got a higher level of proficiency than necessary, than it only counts as 100% else a calculated percentage. Graphically, all together represent the intersection of both polygons of the diagram.
What does column "netted" mean?
If one skill has got a higher level than required, it counts as mathematically calculated, e.g. 120%. Therefore, within the total aggregation, there are netting effects like skill A (120%) and skill B (80%) would result in the total of 100%. That just gives you an idea, if someone is over- or under-skilled for a certain issue, but you have to take a more differentiating look: very good Java Knowledge (technical skill) may not necessary net missing leadership (social skill) depending on the requested profile/skill set!
...