Sometimes, we think adding more resources or people power is always the right solution to speed up a process.

However, is it really the case ? Lets explore some key concept about Brooks' law, explaining how increasing the human factor on a project can have other unwanted results.

What is Brooks' Law ?

It is a phenomenon observable in software engineering and project management where adding people power to a large and generally unsupervised in terms of task disivibility is going to delay such project instead of speeding up the completion.

Key factors and explaination

From Brooks, the following points captures the general (simplified) comprehension of the rule:

1. There is a learning overhead when introducing new actors to a project, especially in software engineering. Introductions of bugs from actors with few experiences on the project can delay progress. It is important to remember that it is not necessarly in terms of overall seniority of a developper's career by example, but rather his time on the specific project and especially if the project is special and was never done before.

2. When working on a task which information needs to be synced with others, a coomunication overhead occurs. This is due to the combination of links between actors, raising in a combinatorial rate because there is one link created for each new actor in the group.

3. Tasks needs to be divisible for the overhead to be close to none. Otherwise, work will generally be slowed down. A famous example: A baby can be made in 9 months, but it cannot take only 1 month by having 9 persons to do so.

How can we avoid this phenomenon in software engineering projects ?

From my perspective and personal opinion, here are possible actions we can take to reduce overheads on software engineering projects:

1. Having a good Agile/SCRUM process and divide tasks without leaving dependances with one-another. Otherwise, actors will have to communicate a lot for trivial information, and you will have to manage a lot of Merge Conflits (GitHub).

2. Offering a global communication channel for genral questions. This way, we reduce the combinatorial aspect of links between multiple actors of a group.

3. Creating a strong documentation process to reduce learning curves and trivial questions of new developers. They will be able to learn and check by themselves when needed, reducing the use of communication channels.

4. Having a balanced management guideline, sometimes having a rigid management framework can reduce or alter a project's progress because of all the overhead it produces. Of course, having no rules will reduce considerably the quality of the software codebase and render metric compilation ineffective. Thus, having a balance between processes and people's autonomy is important, and it motivates the reason why Agile/SCRUM is so popular and effective in practice.

I’ve added some new sections and polished the layout to make it even more user-friendly and engaging for students, colleagues, and fellow researchers.

As seen on the preview picture above, a new segmentation of pages as been done to organize the website.

What is new

Below is an overall description of new additions :

• New Sections: I’ve added more detailed pages to showcase my research, upcoming teaching materials, the latest publications, and many others. Now it’s easier to find the resources you need.
• Improved Layout: The overall design has been refined for better readability and navigation, helping you quickly access what you’re looking for.
• Enhanced Mobile Experience: I’ve made sure the site is even more mobile-friendly, so you can visit it from any device with ease.
• Streamlined Content: Some areas have been updated for clarity and better organization, making it simpler to navigate and explore my work.

Teaching Section : A better Open-Source

I think it is important to share knowledge and make learning available easily. As such, the Teaching Section now contains slides, generic or older assignments, and soon much more. The list contains multiple seminars and courses I have given in the past or actively teaching. As time goes by, more and more content will be added.

Everything is tied up to a GitHub repository to encourage contributions and feedbacks. In case of mistakes or new ideas, please do not hesitate (if you wish) to create an issue on the GitHub repository so I can fix them.

Research Section : More information about my research interests

I started research a bit late because, but I learned that it is an exercise that I'm passionate about.

If you want to collaborate with me on any field related to those of my Research Interests or if you might have any intersting opportunities for me (part time research), please feel free to contact me!

News and Updates

Feel free to drop a follow on LinkedIn, GitHub or put this Website on your favorites if anything of sorts is interesting to you. I will be sure to put my news and updates on any of them!

About

Small section with my professional socials and a small description about myself.

Articles

All of my thoughts and related news.

Projects

Projects I've worked on for fun or for more serious purposes. They normally link to their respective GitHub page or website.

Courses

Courses I graded or tought as a teacher assistant or lecturer during my career.

Resume

My global resume with downloadable options for multiple cases or job types.