GGI Activity: Manage open source skills and resources

Table of contents

Manage open source skills and resources

Activity ID: GGI-A-42.


This activity is focused on software development skills and resources. It includes the technologies and specific development skills of developers, as well as the overall development processes, methods and tools.

A vast amount of documentation, forums and discussions stemming from the ecosystem, and public resources is available for open source technologies. In order to fully benefit from their open source approach, one has to establish a roadmap of its current assets and desired targets to set up a consistent program for development skills, methods and tools within the teams.

Domains of application

One needs to establish the domains where the program will be applied, and how it will improve the quality and efficiency of code and practices. As an example, the program won’t have the same benefits if there is only a single developer working on open source components, or if the whole development life cycle is optimised to include open source best practices.

One needs to define the scope to be embraced for open source development: technical components, applications, modernising or creating new development. Examples of development practices that can benefit from open source are:

  • Cloud administration.
  • Cloud-native applications, how to innovate with these technologies.
  • DevOps, Continuous Integration / Continuous Delivery.


  • Skills and resources required to develop open source software: IP, licensing, practices.
  • Skills and resources required to develop software using open source components, languages, technologies.
  • Skills and resources required to use open source methods and processes.

Opportunity Assessment

Open source tools are increasingly popular among developers. This Activity addresses the need to avoid the proliferation of heterogeneous tools within a development team. It helps define a policy in this domain. It helps optimise training and experience building. A skills inventory is used for recruitment, training and succession planning in case a key employee leaves the company.

We would need a methodology to map open source software development skills.

Progress Assessment

The following verification points demonstrate progress in this Activity:

  • There is a description of the open source production chain (the “software supply chain”),
  • There is a plan (or a wish list) for the rationalisation of development resources,
  • There is a skills inventory summarising current developers’ skills, education, and experience,
  • There is a training wish list and program dealing with skills gaps,
  • There is a list of missing open source development best practices and a plan to apply them.


  • Start simple, grow the analysis and roadmap steadily.
  • When recruiting, set a strong emphasis on open source skills and experience. It’s always easier when people already have an open source DNA than training and coaching people.
  • Check training programs from software vendors and open source schools.


More information:

This activity can include technical resources and skills such as:

  • Popular languages (such as Java, PHP, Perl, Python).
  • Open source frameworks (Spring, AngularJS, Symfony) and testing tools.
  • Agile, DevOps and open source development methods and best practices.

Associated activities: