Management of skills and know-how
Hello Babynus,
For the development of innovative projects, it is very important to have a clear vision of resources and expertise available. This is the key point.
This is important even for other projects in general.
This information will allow a meticulous planning.
It is therefore urgent to add a feature to select the skills and expertise in the creation of a resource and the creation of a user.
Cordially.
Hi,
This is the first step of an already registered request : Ticket #1020 - HR management module.
Due to the important work needed and lesser priority compared to all other requested improvements, this evolution is not planned yet (tagged : to dispatch on V5.x).
If you urgently need this improvement, you may sponsor it : just request for an estimate at support@projeqtor.org.
Hello Babynus,
Let me make an objection on this point: the fact to consider that the knowledge of the resource skills is a question "little bit urgent" or "lesser important" compared to others functions.
One example, in a situation of "risk management" or "problems management ", must be run the "actions plan" but this actions plan will be run by people with the " right skills ".
These are the two terms of this equation.
The Projeqtor tool provides functions for management "problems" and "risks". It follows naturally, the need to identify the skills and expertise needed to solve these "problems" or "potential risks". .
This argumentation is developed, simply, for demonstrate the fact that the need is intrinsic to the project management. This is a general problem of project management. This question is not related to my situation as project manager.
There will be a complete HR module in the future, however there are some reasons to "anticipate " a little .
Cordially.
Hi,
I don't mis-concider "skills" management.
Of course it is an interesting point to know when affecting resources.
But impletation of new functionalities are planned on versions depending on :
- global contribution of the new functionality to the community
- cost (in term or work) of the implementation of the new functionality
- risks on the existing (regressions or performance risks)
- existing workaround for this funcitonality (for instance integration of a wiki in ProjeQtOr is delayed because of already existing good great opensource wikis)
- my own time to spend on development of evolutions : I develop 95% of the code, and ProjeQtOr is not my main activity (I develop and support on my spare time...)
Concidering "Skills" management :
- it is very expensive (would constitute a full version work)
- most enterprises already have their own HR management tool that manages skills
Many smaller evolutions seem more interesting to plan before this one.
Sorry to daly this evolution, but days are only 24h long
...and I took the bad habit to sleep a few hours every night 😉