Use talent analytics and the right technologies to de-risk your projects

Talent Analytics

Do not risk the project because you do not have the right people. Know exactly who you have and need to have.

Technology Analytics

Every additional technology creates opportunities and risks. Make sure that you depend on the right technologies.


Talent Analytics

Most companies start a new project with the question: how do we get the right people? However, the right questions are:

  1. Do we have the right people?

  2. Does the company know what kind of resources it has?

Let’s look at what kind of data an average company has about its resources. Gathering of data starts with the hiring process. The candidate has a resume with all the qualifications. The candidate is hired. Some companies store the resumes in the internal database, but mostly resumes are stored on the laptops of the hiring managers. The first project that the person is assigned to is usually closely related to the person’s skills. The following projects do so much less. Project managers do not have the resume of the person and usually only get feedback from the last manager.

Data on a Touch Pad
va data loss (2).png

At this point, all the information about the employee except for what is the most recent is, gone.


  1. The wrong people are assigned to work on projects

  2. Technologies are not chosen correctly

  3. Consultants are hired to do the work that could have been done by full-time employees.

The result: the project risk is significantly elevated; the budget is increased.

How much does the average company know about its people?

Before evaluating new candidates, the company needs to learn who is has and who it is missing. Let’s look at an example: an IT project that needs to be delivered in 12 months requires several developers and an automation specialist. Automation is a separate specialization; however, many developers learn automation on the side.

Officially, the titles within current team are:

  1. Six developers

  2. One automation expert

  3. Two QAs

To deliver the project on time, the project manager plans to hire three more developers. Is there any risk? With only one automation expert, there is a huge risk. If that person leaves, the project will stall. Ideally, developers would familiarize themselves with the automation; if not, an external resource would learn the current state of automation.

Does your company have any projects that depend on one person? That’s one of the biggest risks for a company.

Solution: VA Analytics. It automatically analyzes data about every project and every employee. It notifies you if it finds any project that has a dependency on a small number of people. It also detects whether those involved lack the right technical skills.


Technology Analytics

How do companies control the use of technologies? They have two main methods:

  1. Architecture team. It is usually an enterprise team that is empowered to provide guidance to the company’s teams. Before any new project launches, the team needs to present an architectural solution to the architecture team. Architects make sure that the design is aligned with the company’s strategy. If the team wants to do something new or highly unusual, then it needs to prove that it is necessary to the architecture.

  2. Monitoring source code. There are multiple tools that can periodically scan source to find any new libraries being used. The main objective is to find libraries that have known security vulnerabilities.


Neither option addresses the two main problems:

  1. Automation of discovery. Let’s say a developer adds a technology to the stack. How would the architecture team find out? In most cases, there is no automated way of doing it. Architecture needs to wait for the next review or someone to mention it to them.

  2. Dependency on technology. Let’s look at an example: a new feature that is based on AI is introduced to the product. It successfully passes through IST, UAT, and it is on the way to being used by the end-users. Before the technology is used in production, the company needs to evaluate the associated risks. Let’s look at two companies. The first company is a new AI startup. Its only product is used to analyze emails, and it is fully based on AI. The second company sells an email server. It has introduced its first feature that is based on AI. The AI aspect was built by a Ph.D. in Statistics with the help of multiple developers. The developers did not do the AI; they prepared datasets, built the API, etc.

Which company has a higher risk?

Clearly, the second company risk is significantly higher. One person leaving can jeopardize the company’s reputation.

Solution: VA Analytics. It automatically discovers all the technologies used at the company. Management is provided up-to-date information about projects’ dependencies. It is also automatically notified if there is an over-dependency detected.

See the use case Regulatory Project for more information.