Agile approach in scientific research

Scientists will confirm that a research project often deviates from the original research proposal. Scientific research is executed messier than following a strict series of consecutive planned activities. This leads to the conclusion that research is not very well planable. The waterfall method has not been flexible enough to be applied to scientific research.

In a research proposal, there is a good chance that the work is planned as a list of consecutive activities, often visualized in a Gantt diagram. The idea behind this project management approach is to split one large activity into a series of smaller, more achievable activities, where every phase of a project usually only starts when the previous one is complete.

On the other hand, the Agile approach gives more priority to flexibility. The software development sector has radically changed by the Agile philosophy. In the meantime, the Agile approach is also used in many other areas outside software development processes ranging from, for example, schools to criminal investigation.

With an agile approach an early but partial result, which can be improved at a later stage, is more important than a "perfect" result that can only be achieved at the end of the project. After all, feedback that comes to the intermediate result can be used to adjust in the further research process.

Agile approach among scientific experiments

Despite the fact that scientists are the source of many technological innovations, academics seem to be adopting the Agile approach slowly. However, the Agile approach has much added value if it is applied, for example, when performing scientific experiments.

In scientific research, it often happens that a series of experiments must be carried out to test a hypothesis. In a waterfall approach, this long-term activity is split into a series of consecutive activities. A detailed planning is made of all experiments. This includes implementation, data processing and interpretation. Only in the final phase of the work is achieved there will be real scientific insight.

A protocol for scientific experiments could also be carried out according to the Agile approach. We can distinguish the following steps:

• Splitting work

• Sprint planning

• Sprint execution

• Regular scrum

• Sprint review

• Sprint retrospective

Splitting work

It is important to split the work into multiple sub-activities, where each part is characterized by a concrete and feasible result. Each part is executed in a limited and fixed period that we call a sprint. In principle it is agreed how long that period lasts, where the duration will partly depend on the duration of the experiments that must be performed. The period ranges preferably from two weeks up to several months. The following guidelines can help in defining partial activities:

1. Plan within a sprint the execution of a small number of coherent experiments that can be completed by direct data processing and interpretation. The intermediate result provides a partial insight that is valuable for testing the hypothesis.

2. In successive sprints it is possible to increase the number of variables to be investigated. This will lead to the implementation of new experiments and merging the new and old data which leads to new data interpretations.

3. In successive sprints it is possible to increase the number of data to be acquired per variable to be investigated. This will lead to the implementation of new experiments and merging the new and old data which leads to new data interpretations.

Sprint planning

The supervisor, the research team and any other stakeholders, such as a postdoc, industrial partner or master's student, comes together in a short conversation of about 30 minutes with the aim of defining the sprint. For example, a goal of the sprint can be a research goal of a series of experiments and the duration of each experiment. Everyone agrees on these points, so that expectations are aligned and the entire research team pursues one joint goal.

Sprint execution

The research team has the maximum focus on the defined purpose. It is important to perform the experiments, data processing and interpretation in limited time.

Regular scrum

The research team comes together for a maximum of 15 minutes at a fixed moment in time. For long-term sprints it is possible to get together every week. Choose the same time slot and outside conventional working hours to ensure that no other obligations are in the way, such as meetings or educational activities.

This meeting must be short and efficient, without laptops or paper. For example, meet that everyone stands (i.e. stand-up). Only three questions have to be answered:

1. What has been done since the previous scrum to contribute to the goal? For example, discuss which experiments have been performed.

2. What will next period be done until the next Scrum to contribute to the goal? For example, which experiments are performed.

3. What are the impediments? For example, is the scientific arrangement suitable or are all necessary materials present.

Sprint review

At the end of the sprint you meet all stakeholders to discuss the results and whether they are in line with expectations. Take the time to enter detail and brainstorm together.

Sprint retrospective

Discuss the encountered process impediments so that the next sprint can be performed better than the previous sprint. This phase is needed to solve problems. Honesty and transparency are crucial. Agile revolves around adjustments: plans can change. Go back to step one and restart the schedule, addressing the next working layer in a new sprint.

In conclusion

Keep in mind, that one-size-fits-all strategies do not apply to scientific research. This Agile approach is not a comprehensive tool that magically will serve every purpose. It must be seen as a starting point that is intended as an inspiration for a different approach to managing scientific research. For many it helps to go back to the Doctorate with a renewed, Agile Mindset.

For those interested, Agile in Focus can advise when applying the Agile approach. Agile In Focus also offers training courses where practical examples and tips are shared. We are ready to help you further.