Ready to try Agile for research?
Join our upcoming study

A PhD (or any research project) can feel at times as long and tiring as running a marathon. Yet, as we explained in this post, there are techniques you can use to alleviate the pain and turn your project into a series of dynamic sprints.

Laura Pirro, PhD candidate at Ghent University, realised the potential that Agile project management could have in academia. Agile has revolutionised the software-development sector and it is now used in many other areas (from manufacturing industry to the FBI). Why not using Agile for academic research too? In many aspects, academia is different than industry but Agile philosophy can still be applicable. Laura has worked on adapting Agile to research: you can find the details of the methodology she proposes in this post that she wrote for Nature Careers.

Agile for research has already proven success in Joris Thybaut’s research group at Ghent University (where Laura is pursuing her PhD). We are now looking for enthusiastic researchers and professors who would be happy to test Agile for research during a few months and let us know their results.

How could Agile for research work for you?

If you are a student

As a student, you probably understand that your advisors/supervisors are incredibly busy people with tight timetables. Still, you work hard on your project, and you often need advice on how to proceed with your research. However, setting up a meeting with your supervisor whenever you encounter an issue may feel like a struggle: it sometimes takes so long that by the time you get to meet her/him, you have already figured a way around the problem (although sometimes it might not be the ‘right’ path, so you need to go back and redo some stuff).

Agile for research will allow you to have continuous feedback on your activities in an effective way both for you and your supervisor. First, it will ‘force’ you to organise sprint planning meetings with all the stakeholders involved in your project: supervisor, postdoc, industrial partner. master student… in order to get everyone to agree on the goal and the duration fo the sprint. Thereafter, you will have short (15min) scrums every week with your supervisor so as to answer three questions: what was done the previous week to contribute to the goal? What will be done next week to contribute to the goal? And, are there any impediments? Finally, once the sprint is finished, you will meet again all the stakeholders for the sprint review, retrospective and planning.

If you are a professor/supervisor/student advisor

Following the work of students can be incredibly time consuming and difficult to fit in in your timetable. Furthermore, it is frustrating to dedicate time to students who (sometimes) still seem lost and have an unclear idea of what exactly they should do in their project. These tasks get even harder as the number of supervised students increases.

Agile for research will allow you to structure the way you communicate with your students. In a collaborative effort, the project is divided into layers of activities with an estimated duration of 2-12 weeks. In the sprint planning meeting, the specific goal and duration of the activity is decided with all the stakeholders (student, industrial partner, postdoc, etc.). Thereafter, you will follow the work of your students with short weekly scrums of only 15 minutes. Finally, in the sprint review, retrospective and planning all the stakeholders come back together to remove impediments, adapt to changes and plan the next sprint.

Does this sound appealing? Get in touch with us!

If you believe that Agile for research might be interesting for you, please get in touch with us or with Laura Pirro! We are conducting a study to see how this methodology fits in academia and we would be happy to solve any questions and provide additional information. We look forward to hearing from you!

What if your PhD didn’t need to feel as long and tiring as a marathon?

In many ways, pursuing a PhD resembles running a marathon: long distance, loneliness and fatigue are seemingly insurmountable obstacles and nobody can hope to reach the end without adequate training. [Actually, according to ancient literature and mythology, one non-professional athlete ran the first Marathon in full armor in the Greek August weather (Lucas, 1976), but he paid the effort with his life! This certainly does not set a positive example for all of us, aspiring PhD holders…].

Continue reading “What if your PhD didn’t need to feel as long and tiring as a marathon?”

Not in the mood to write? Why you should still show up, even if the muse doesn’t

Let’s face it, us, scientists, are passionate about our job. We are usually delighted about carrying out our scientific tasks (experiments, simulations, reviews, etc.). But when it comes to writing our findings, the motivation goes down. We rarely feel we’re ready to write and we rarely feel in the mood to write… the consequence: when we sit down and are supposed to write, we rather start doing other things, we procrastinate. And of course procrastination comes guilt and frustration. Until the deadline dangerously approaches: then, in the last minute, creativity pops up. Well, let us break it for you: that’s not really last minute creativity, that’s stress and adrenaline doing their job.

In our Road to Bootcamp series of posts, we’ve already covered how starting writing your work early enough will let you fully benefit from the ‘magic’ of the writing process; therefore, reducing procrastination. In this post, we’ll focus on how creativity can be boosted—even when you’re convinced that you’re not in the mood to write.

Continue reading “Not in the mood to write? Why you should still show up, even if the muse doesn’t”

The evolutionary brainstorming: do it as your brain was wired to do it

  1. You have probably been in many brainstorming meetings where you encountered one of the two following scenarios:
  2. “Dear colleagues, what are your ideas on this project…”, followed by a long silence, as if there was a brainstorming switch to turn on;
  3. You suggest an idea and immediately someone is saying: “No, this is not possible, it’s not a very good idea!”.

These two scenarios gather the two main pitfalls of effective brainstormings: priming and judging. Continue reading “The evolutionary brainstorming: do it as your brain was wired to do it”