Methodology at the service of the result

While there are a number of methodologies for managing a project, current discussions are based on Which one is better?This, coupled with the difficulties encountered in implementing the new structures, makes the decision increasingly complex. Before delving deeper, let's look at an important criterion.

The context

If we were to consider life as a video game where we have 100 points to enhance a skill, we could distribute them between Strength, Emotional Intelligence, or Logical Intelligence, How do you distribute it?

The truth is that it depends on the context. If there were an accident and a loved one was trapped under a car, the 100 points would probably go to strength, to lift the car. If, on the other hand, someone close to us was going through a difficult time, all the points would probably go to emotional intelligence, to help support and comfort them. If, on the other hand, we had to take a logical-mathematical exam, the 100 points would probably go to logical intelligence.

What I'm trying to say is that basically, before making a decision Context can have a drastic influence in the result.

The same applies to methodologies; often the context can guide us in determining what strategy should we follow? to obtain the best possible result.

A bit of history

In recent years, there has been a massive surge in the use and adoption of agile methodologies [1], where agile methodology is understood as the established framework (such as scrum, kanban, lean, among others). Especially in Latin America, it seems to be a development towards the future, hand in hand with digital transformation and innovation, but with this, various debates have arisen about which methodology is better than the other, whether predictive or adaptive methodologies.

The reality is that neither is better than the otherHowever, certain points should be considered before choosing which one could give us the best results.

Selection criteria

It may seem difficult to choose and understand which criteria to consider when determining a work structure, but it is not so complex if you know where to look.

The first thing is the scopeAgile methodologies are designed to solve complex problems through lightweight solutions to generate value [2] as stated in the Scrum guide itself. Therefore, if the scope is not very clear, if there are frequent changes in priorities, or if there are often difficulties in defining it, the best thing to do is a agile methodology, since it denotes a complex problem that is not so easy to determine.

On the other hand, when the scope is defined and limited, it is best to use a predictive methodologyPredictive methodologies, like waterfall, are clearer, less ambiguous, and more defined. They don't allow much room for changes during project execution, but that doesn't mean it can't be done; it simply means the process is more bureaucratic and requires clearer definitions for change controls.

Another important factor is the openness to changeIt can also be classified as maturity. Implementing an agile methodology that breaks established paradigms requires a change of mindset significant, that is, generating an agile mindset, which often creates resistance to change.

He time and cost There are usually other factors that determine which path to follow; often the fastest option is chosen, which does not necessarily lean towards one methodology or another, but is sometimes influenced by what the team knows how to do, since it avoids learning curves.

Additionally, understanding the nature of the company and criticality The project's implications can also be reflected in the election, because there are industries that, due to audits or regulations, must be attentive to implementing changes quickly and promptly.

Given this shared thought among several theorists, the term “Tailoring” [3] was included, implemented in PMBOK 6, which precisely indicates how to adapt some of the methodologies towards the result.

It is important to understand that the adaptation of different methodologies, generating hybrid models or models better suited to each nature of a project, is not due to a change for convenience, but because efficiency and always oriented towards a result or purpose

Faced with this discussion, at Zenta we adopted a agile mindsetHowever, we always consider both methodologies, adapting quickly to the client's needs and culture, taking into account the nature of each project and environment. Our results-oriented approach allows us to create successful projects while considering the factors mentioned above.

Therefore, we adapt in the most efficient way to each individual's needs, leaving the door open and the foundations solid, focused on the digital transformationThis will allow customers to guide their journey and chart their destination based on results.

As a recommendation: Follow your instincts

As has been reviewed, the truth is that it is indicated in the project management community It is never an absolute truth.Therefore, they should not be inflexible and rigid regarding the methodology they choose to implement.

Therefore, evaluate, analyze and conclude based on the project's progress and development, so you can better determine what to add or remove, depending on what contributes most to an ideal outcome.

This instinct isn't something you can read and learn; it's something you must hone only with experience. practice and execution, Understanding the emotions, motivations, fears, and obstacles that each individual client possesses will help you sharpen your senses to better identify the situation and determine what is most appropriate.

This does not mean in any way that the methodology is wrong, but it is important to study and understand the foundations on which it was created; this will provide a holistic understanding based on management principles, and will help you acquire new and better tools at your disposal, which will be readily available when needed.