blog

The Agile Research Guide: Reimagining research through agile principles

Image:
Agile

A familiar frustration…

Picture this: You’ve spent months crafting the perfect project proposal. The workplan is looking sleek, the interdependencies have been thoroughly considered and the Gantt chart reflects this nicely: every deliverable is clearly defined, and the timeline is ambitious yet achievable, or so you’re convincing yourself. Fast forward to the project’s launch, and reality hits. Stakeholders’ needs shift. New insights emerge. Political priorities evolve. Suddenly, the rigid plan you so carefully constructed feels more like a straitjacket than a roadmap.

If this sounds familiar, you’re not alone. Many research projects experience the same disconnect between what’s planned and what’s possible or, more importantly, what’s useful. Traditional project management, with its linear timelines and fixed outputs, often struggles to keep pace with the dynamic nature of research, especially in applied or user-centered contexts. The result? Reports gathering dust, tools left unused, some frustrated scientists and end-users, and missed opportunities to make a real-world impact.

The problem with predictability

Research, by its very nature, is unpredictable. Whether it’s a sudden policy shift, an unexpected stakeholder need, or a groundbreaking insight, the path from proposal to delivery is rarely a straight line. Whether from intuition or from experience or both, we know this. Yet, many projects still rely on linear planning approaches and tools like Gantt charts, which assume that every step, each interdependency can be foreseen and scheduled in advance. This approach not only ignores the inherent uncertainty of research but also risks producing outputs that are outdated or irrelevant by the time they’re delivered.

The consequences are clear: projects that fail to adapt often fail to deliver meaningful impact. For funders and policymakers, this means wasted resources and missed opportunities to address pressing societal challenges. For researchers, it means innovative ideas and insights that never reach their full potential.

A shift in research culture

Over the past few decades, EU funded research projects have seen a transformation in how research is conducted. The focus has shifted from purely academic initiatives to hybrid models that blend academic rigor with real-world applicability. This evolution demands nimble, more iterative processes, greater stakeholder engagement, and a wider variety of outputs: think policy briefs, interactive tools, and co-created solutions, not just peer-reviewed papers. Under the Horizon Europe programme - EU’s key funding programme for research and innovation - Europe has taken initiative by instoring the multi-actor approach, emphasizing the importance of impact and more recently by introducing the lump sum funding approach.

Yet, despite these shifts, project management in research has much room for improvement. The needed change not only requires good processes, it requires a change of mindset.

Linear planning is still the norm, even though it’s ill-suited to the fast-moving, user-driven projects of today. The gap between how projects are planned and how they unfold in practice is widening, and it’s time to bridge it.

Enter agile: a solution born outside research

The concept of agile project management originated in the software industry in 2001, when a group of developers drafted the Agile Manifesto. This groundbreaking document outlined four core values:

  • Individuals and interactions over processes and tools

  • Working products over comprehensive documentation

  • Customer collaboration over contract negotiation

  • Responding to change over following a plan

These values were a direct response to the rigid, waterfall-style project management that dominated software development at the time. Agile prioritized flexibility, collaboration, and iterative progress; principles that quickly proved their worth in fast-paced, innovative environments.

Since then, agile methodologies have spread far beyond software. Industries from manufacturing to marketing have embraced agile’s emphasis on adaptability, user feedback, and continuous improvement. Yet, despite its proven benefits, agile remains a rarity in the world of research.

Why agile belongs in research

The principles of agile align perfectly with the needs of modern research projects. Here’s why:

Flexibility: an iterative approach allows teams to pivot quickly in response to new insights or changing stakeholder needs.

User-Centricity: involving end-users early and often, ensures that outputs are relevant, practical, and impactful.

Transparency: regular feedback loops and open communication keep everyone aligned and accountable.

Efficiency: breaking work into smaller, manageable cycles (or “sprints”) reduces the risk of wasted effort and increases the likelihood of delivering useful results.

For policymakers and scientific project leads, agile offers a way to move beyond the limitations of traditional project management. It’s not about abandoning structure, it’s about creating a structure that works in the face of uncertainty.

The INTERLACE experiment: agile in action

The INTERLACE project, a four-year EU-funded initiative focused on urban ecosystem restoration, provides a compelling pilot in how agile can transform research. Facing the same challenges of rigid planning and diverse stakeholder needs, the INTERLACE team decided to experiment with agile methodologies.

The results were striking. By adopting iterative workflows, the project team was able to:

  • Involve end-users early and often, ensuring outputs met real-world needs.
  • Adapt to new insights and policy shifts, keeping the project relevant and impactful.
  • Improve accountability to both stakeholders and funding agencies, thanks to transparent, feedback-driven processes.

INTERLACE demonstrated that agile isn’t just for software developers, it offers powerful tools for any project that needs to balance rigor with real-world relevance.

Your agile journey starts here

If you’re a researcher or scientific project lead, you might be wondering: How can I bring agile into my own work? The good news is, you don’t have to start from scratch. Our Agile Research Guide will provide  answers to your most pressing questions and some insight on the mindset shift needed to implement agile in your projects. We will also follow up with a more in depth online agile module which dives deep into the practical steps, tools, and which will focus entirely on the context of research.

In the current Agile Research Guide, you’ll find:

  • An introduction to Agile in research contexts
  • Real-world examples from the INTERLACE project
  • Key insights and lessons learned
  • Open questions for future research projects consortia

 

Download the guide