What do you do if you need to choose a project management methodology for R&D?

1 Factor 1: Project scope

One of the first things to consider is the scope of your project, which defines the goals, deliverables, and requirements of your R&D work. Depending on the nature and size of your project, you may need a more or less flexible and adaptive methodology. For example, if your project is exploratory, innovative, or risky, you may benefit from a more agile approach that allows you to test, learn, and iterate quickly. On the other hand, if your project is more predictable, stable, or regulated, you may prefer a more traditional or hybrid approach that follows a predefined plan and structure.

2 Factor 2: Project team

Another important factor is the composition and dynamics of your project team, which affects the communication, collaboration, and coordination of your R&D work. Depending on the skills, roles, and preferences of your team members, you may need a more or less formal and hierarchical methodology. For example, if your team is cross-functional, self-organized, or co-located, you may benefit from a more lean approach that empowers your team to make decisions and deliver value. On the other hand, if your team is specialized, distributed, or outsourced, you may need a more structured or waterfall approach that defines the responsibilities and dependencies of your team.

3 Factor 3: Project stakeholder

A third factor to consider is the involvement and expectations of your project stakeholders, which influence the feedback, support, and evaluation of your R&D work. Depending on the level of interest, engagement, and alignment of your stakeholders, you may need a more or less transparent and responsive methodology. For example, if your stakeholders are internal, active, or supportive, you may benefit from a more scrum approach that involves them in regular reviews and retrospectives. On the other hand, if your stakeholders are external, passive, or demanding, you may need a more stage-gate or phase-gate approach that demonstrates the progress and quality of your work at predefined checkpoints.

5 Methodology 2: Traditional

Another common methodology for R&D is traditional, which is a rigid and sequential approach that follows a linear and logical process. Traditional methods, such as waterfall, PMBOK, or PRINCE2, are based on a series of phases and activities that define the scope, plan, design, execution, and closure of your project. Traditional methods are suitable for R&D projects that are simple, stable, or regulated, as they provide a clear and consistent framework and documentation for your work. However, traditional methods also entail a high level of risk, waste, and resistance to change, as they assume that you can predict and control all the aspects of your project upfront.