What do you do if you're unsure which project management methodology to choose?

Conducting a needs assessment is foremost critical to thoroughly verify requirements, objectives and constraints (scope, time, cost among others) of the project. This should go hand in hand in the quest to assess stakeholder needs and project characteristics to determine which methodology to use. The nature of the project and the stakeholder requirements is critical to identify the choice of methodology to use. Within the technology domain, I would mostly use waterfall due to the sequential nature of requirements to execute the project whereas in most software projects, agile would work due to the possibility to implement concurrently. Hybrid in some instances would also work especially where there is a need for both methodologies.

Analyse the project's scope, timeline, budget, and team dynamics. Is it a well-defined project with clear deliverables (waterfall might be suitable) or one with evolving requirements (agile could be a better fit)?

Existen varias metodologías, pero uno de los primeros puntos es clarificar el alcance de un proyecto y tenerlo bastante claro, y según si el proyecto es más o menos complejo, sean en personas, tiempos, esfuerzo, debe colocarse más o menos puntos de control y con ello delimitar lo necesario.

The key is to evaluate the program requirements, team dynamics, and stakeholder expectations to guide your decisions. Understand: 1) Your industry: Consider if you're in an industry that changes frequently on a cyclical cycle. 2) Your project focus: Consider the objectives of the projects. 3) Determine the complexity of projects: Are the projects on the more complex side, or are they usually straightforward?

Pour l'une de mes premières missions, j'ai accompagné une grande entreprise industrielle qui se demandait comment limiter le taux d'échec de ses développements de nouveaux produits. Marketing et R&D utilisaient une méthode de développement de projet classique, et programmaient la sortie du produit et la cha?ne de production qui allait avec. Résultat, 70% d'échec car ils se rendaient compte beaucoup trop tard de l'impossibilité de produire à grande échelle telle ou telle innovation. Avec une méthode de projet agile, ils pouvaient détecter plus t?t les problèmes de production et éviter d'immobiliser une cha?ne de production pour rien. Une méthode projet doit donc bien correspondre aux besoins de chaque projet!

Evaluate your team's skillset and experience with different methodologies. Do they have experience with Agile frameworks or are they more comfortable with a Waterfall approach. Consider your team's preferences and what methodology they feel would best suit their working style and communication dynamics.

Lorsqu'il faut choisir une méthodologie de gestion de projet, bien s?r il faut sélectionner une méthodologie compatible avec les exigences du projet, mais il ne faut jamais oublier que le collaborateur est primordial. Chaque partie prenante au projet doit être capable de suivre la méthodologie projet. Or, en tant que consultants nous sommes familiers de plusieurs méthodologies et nous avons tendance à croire que la prise en main d'une nouvelle méthode est "facile". Ce n'est pas le cas. Il faut donc consulter l'équipe, et peut être choisir une méthodologie moins performante, mais qui sera mieux utilisée. Mieux vaut une renault twingo conduite à la perfection, qu'une ferrari qui cale parce qu'on a du mal à passer la 2nde. :)

Evaluate project team's experience and comfort level with different methodologies (e.g., Agile vs. Waterfall). Opt for a methodology that leverages their strengths and fosters a smooth workflow. Example: Managing a website redesign for a company. The project has clear goals but might require some design iteration. Here, a hybrid approach might be ideal. You can leverage Agile for the development phase, allowing for flexibility in design revisions, while incorporating Waterfall elements for upfront planning and a defined launch date.

Identify potential risks associated with the project, such as changing requirements or unforeseen technical challenges. Evaluate how different methodologies address these risks. For example, Agile methodologies provide greater adaptability to changing requirements. In my past EV project, considering the possibility of scope changes during the site design, I concluded that a Waterfall approach, with its rigid structure, could hinder flexibility. An Agile methodology, like Scrum, would allow for iterative development and easier course correction if needed.

Assess the availability of resources, such as personnel, budget, and technology, to support different methodologies. Agile methodologies typically require more upfront investment in planning and collaboration. Consider the project timeline and how different methodologies impact the delivery schedule. Waterfall offers a more predictable timeline, while Agile prioritizes flexibility over strict deadlines. In fleet electrification project we had a relatively tight deadline, but also required ongoing client feedback. An Agile approach with shorter sprints allowed for continuous progress while incorporating client input throughout the development process.

Learn about popular methodologies like Agile, Waterfall, Scrum, Kanban, or Lean. Understand their strengths and weaknesses to see which best aligns with needs of the project.

Throughout the project lifecycle, be prepared to re-evaluate your chosen methodology if circumstances change or unforeseen challenges arise. Don't be afraid to create a hybrid approach by combining elements from different methodologies to suit the specific needs of your project. While we primarily used agile framework for the fleet electrification project, we incorporated elements of Waterfall for specific deliverables that required a more structured approach, such as environmental planning.

Involve the client in the discussion and get their input on their preferred level of involvement and desired level of flexibility throughout the project.

The best methodology is the one the team is confortable with. In theory some methodologies adapt better to certain types of projects than others, however if the team is not familiar with that methology, the team may not be able to achieve the potential of the new methodology; on the other hand, with a methology the team is familiar with, full potential can be acheived and there will be less chance of mistakes.