How do you select and compare project management frameworks?

In my experience, if you try to impose a linear more sequential approach on an innovative project, this will lead to disharmony and disfunction within the team which will then lead to global disbelief in the management’s tools, processes and vision. It is crucially important to asses the type of project before deciding which approach to adopt.

o choose the best project management framework, consider alignment with project goals, scalability/adaptability, resource/skill requirements, stakeholder engagement/communication, risk management, and organizational fit. Ensure the framework supports desired outcomes, accommodates changes, leverages available resources, promotes collaboration, manages risks, and integrates with existing practices. Conduct analysis, seek professional input, and pilot projects to determine the most suitable framework.

When it comes to project management, choosing the right framework can make all the difference in achieving success. But how do you go about selecting and comparing these frameworks? ?? In my experience, the first step is understanding the unique requirements and objectives of your project. Each framework has its strengths and focuses on different aspects, such as agility, documentation, or stakeholder engagement. By aligning your project's needs with the strengths of a framework, you set a solid foundation for success. Next, consider the scalability and adaptability of the framework. Projects evolve, and the chosen framework should be flexible enough to accommodate changes and growth.

Communication is paramount. It begins with the stakeholders and getting granular with them to identify what is they truly want. Value to the customer is the PM's priority, and identifying the stakeholder's value definition is what I call - "setting conditions." Once the conditions are set and you identified what/where the stakeholders hold value the project framework becomes exposed. This approach allows the stakeholders to draw the same conclusions how to engage the project the PM already have - moments before the meeting.

In one particular project, I organized a co-creation workshop where users and stakeholders collaborated in designing the ideal user journey. This not only fostered a sense of ownership among users but also allowed us to gain deeper empathy and uncover valuable insights that significantly shaped the final product.

When implementing frameworks, be sure to get sponsorship from leadership or executives over the affected area. Change can be challenging, and if the teams you work with don't have any incentive to adapt, adopting a framework that everyone uses becomes difficult.

It is OK to be predictive with your project should the team, culture, and products align with it. Agile is great; however, so is Scrum, Kanban, Prince, etc. A PM does not have to rush to the "flashy new toy (agile) if it does not align with the project. Conversely is the same; do not force predictive with a more innovative project. A PM focuses on 3 areas to ensure compatibility with their teams and stakeholders: 1. Effective and controlled method(s) of communication 2. Resources (templates, charts, sheets, etc) That are understood by EVERYBODY - common operating picture 3. A repository to cache lessons learned and pull from for future projects.

Lean principles apply here: focus on the minimum necessary framework components to implement the project or program. When the program has too many extra things to manage, it becomes a chore for the person running it and a mess for stakeholders to understand.

Flexibility and scalability are crucial considerations when selecting a project management framework. Assess how well the framework can adapt to changing circumstances and needs. Look for indicators such as the framework's ability to accommodate external factors, incorporate feedback, and adjust plans and deliverables. Evaluate whether the framework can scale up or down smoothly without compromising quality or efficiency. Choose a framework that enables you to respond to change and uncertainty effectively.

Another important criterion is to review the evidence of the effectiveness of the framework for similar or relevant projects. This involves researching best practices, case studies, testimonials, and recommendations from other project managers or organizations. Look for endorsements from reputable project management associations or institutions that highlight the framework's value. The indicator for evidence of effectiveness is the framework's proven results, benefits, or value demonstrated in real-world projects.

Trust the Project Manager’s Approach At a company I worked at, myself and the other Project Managers on my team were forced to use one specific project plan framework template for every client project. We could not use our own judgement about what approach to take, as the criteria were set before we even learned about the project. As you can imagine, this caused frustration amongst clients who did NOT fit in this framework. My advice to employers is to trust your Project Managers and allow them to pivot the framework when needed to fit the customer’s needs (not make your customers fit into it). Consider switching to a new framework software if your current one is not allowing for this type of agility (as was the case at my company).