Management methods for software programming and doing research

This section will present some methods, mostly coming from computer programming, but also more general ones, that can be applied in the context of research [1].

Science often uses methods and procedures for data analysis or publications, but the daily aspect of conducting research are usually up to the people. The methods presented in this chapter can, I believe, be applied, or at least adapted, to some aspects of research, whether it is to conduct collaboration work, or ensure the proper follow-up and mentoring of students.

The use of these methods and tools can make conducting a project with an Open Science outlook easier, and ensure the reproducibility and continuity of research [2].

At the very least, you’ve been warned that this how I function generally.

• Workflow cycle inspired from Integrated Safety Management
• Gamification: Seeing projects as an adventure
• The Pomodoro method
• Lean software programming
  • Practical implementation
• The Zen of Python
• Note-taking
  • On paper
  • On a computer

Footnotes

[1]

Not all management methods from outside the research community should be adapted. For example, the Six Sigma techniques, with a focus on minimizing variability, would be a disaster if applied to a research project.

[2]

“Research continuity“ is not just about keeping your analysis files organized, but following procedures, standards , and best practices, to ensure that all the information on a research project is kept. This is particularly important when short term collaborators are involved (i.e. students, postdocs, …) so that others can pick up their work where they left it when they move on to other positions/labs/… That also applies when your computer crashes, or your thumbdrive with a very important presentation is lost: what have you done to ensure that the work itself is resilient when the physical support fails.