Project Management Central

Please login or join to subscribe to this thread

Topics: Business Analysis/Requirements Management
Need ideas to create an internal expert register


I just arrived in this community, and this is my first topic.

I hope this is not too basic for you guys :)

Here is the issue I have in my organization.

It is a software organization, and we have a big specialized accounting software with many modules.

So the developers have different knowledge, depending on what they usually work on.

The thing is, it is sometimes hard to tell which person is the expert in which area of the software.

And I was wondering how to address this issue.

Do you think it would be a good idea to create a kind of "expert register", where the expertise of each developer are clearly defined ?

Maybe this asset is already described in the stakeholder knowledge area of the PMP. But right now, I can't tell which.

Your ideas are welcome !

PS : we talked a lot about this kind of register with my hierarchy, but each time we speak about it, I have the same answer : "Yes, it would be good, but we don't have time right now to create it".

Sort By:

Hi Alexandre,

In my view, I think it would be a good idea to create an "expert vegister", as you say, where the expertise of each developer is clearly defined.
This tool will help you to organize the team in the project and in the future ones.

Best regards.

Alexandre -

A skills inventory is a good idea when dealing with a large group of diverse skills and limited supply to meet demand.

I'd keep it simple - a table with the skills in the columns and people's names in the rows. Folks can indicate their skill with a 1-5 scale, and if they are interested in learning a skill they can indicate that with a different symbol.


I think your question is more related with PMBOK resource management than stakeholders. maybe have a look at chapter 9.3 'acquire resources' and search for skills and experience.

Thanks everyone for your answers ! This helps me a lot.

@Kiron : I like your idea about a skills register ! It has many benefits. Only risk I think : that resources perceive it as an intrusive way to monitor their performance. But I will definitively speak about your model in next meeting with my hierarchy.

@Mirko : thank you ! I am still studying the PMBOK right now. Your remark makes sense. I need to have a look in this section.

I agree with Kiron's idea and also the risk mentioned. This may not be shared with all team members. However you can use the register for many purposes such as
(1) Whom to discuss while planning?
(2) Check which skill set needed for the project is missing or not adequate and plan the training if needed.
(3) See where you have more dependency and plan to up skill others since having dependency on one or two resources will be a risk.
(4) Can use for performance evaluation on whether the performance was according to expert level and if not what are the areas of improvement.

Please login or join to reply

Content ID:

Eighty percent of success is showing up.

- Woody Allen