Meet a member of the Squash team

Interview of a developer of the Squash team: organisation, development technologies and  environnement

Behind the continuous improvement of Squash TM, there is a team coming from different area of expertise. Today, Benoît – member of the Squash team since 2010 and main developer of the plugin Squash4Jenkins – tells about his professional experience,  the organization of the Squash team and the technologies used to develop the test management tool.


Hello Benoît. Maybe you can start by telling us about your education?

First, I graduated from a master specialised in AI research. I did internships in robotics and autonomous navigation. Then, I decided to take a thesis in Orsay, and passed a PhD in computational neuroscience.

Even though it has been a very interesting topic to study, I was not looking to continue further in this field. I wanted to convert in engineering jobs.


How did you proceed to do so ?

I have been looking for a complementary training in engineering. I found several websites offering different kinds of training and it appears the 6 months cursus provided by the AFCEPF (a French educational institution specialised in Software engineering) was answering the best my expectations.

I have been hired by Henix after this cursus.


Can you tell us what your first missions for the company looked like?

2010 is a key time for Henix: the company is just starting its new activity as a software publisher. Back then, Squash TM, the test management tool, is barely a POC.

I have been hired to reinforce the Squash team. The first 5 years are exclusively dedicated to the conception and to the development of Squash TM. After that, new tasks came to complete the work of a developer in the Squash team. Today, those tasks constitute my daily work.


So, can you tell more about today responsibilities you are in charge of?

I am not only working on the conception and the development anymore. I am also in charge of:

  • Technical consulting – To answer clients’needs for consulting or expertise.
  • Training – To help clients to develop their own extensions of Squash TM.


Today, how many members are there in the Squash team?

The development team for Squash is composed of a Scrum Master, a Product Owner, 8 developers and a tester.

But the Squash team, it is also a team dedicated for the support, a Professional Services entity and a Marketing team.


What is a typical day for a developer?

We could say there are three main tasks:

  • The development

A new version of Squash TM is released every six months. We work daily at the development of new functionalities in order to insure the continuous improvement of the tool.

  • The support

A developer can be needed to answer specific clients’ needs. All demands relative to the support have priority on any other task.

  • The code review

Friday is dedicated to the code review of Squash by peers.


How is the team organised to work on the development part?

Most of the time, a developer is responsible for one functionality. Obviously, it also depends of the charge of work to develop the functionality.

The team works according to agile method : we have regular conversations between the project owner and the project management, we do stand-up meetings to status everyone’s work. We do sprints to develop new functionalities, with delivery and feedbacks after each sprint.

All the members in the Squash team are full stack: we do have the ability to intervene at any level of development of the application.


Can you tell us a few words on the technologies and environment used to develop the Squash suite?

For Squash, we work on IntelliJ, a Java IDE.

About the technologies, the most important ones for the hosts are Hibernate (an ORM), Spring (for web and integration), JSP and Thymeleaf (to generate HTML).

The client is build on JQuery and Backbone.

We host sources on Bitbucket.

As Continous Integration Plateform, we use Jenkins. SonarQube is used for qualimetry and Maven as technology for builds


What is the next challenge to come for the team?

Right now, we are seeking to reinforce the integration between Squash & JIRA for a better coordination between the development team and the qualification team for projects in agile. You will know more about it in the next versions to come 


Thank you Benoît for sharing your experience and knowledge. We look forward to knowing more about the next version of Squash TM.


Joomla SEF URLs by Artio
FaLang translation system by Faboba