In recent times I got the impression, that people tend to manage projects with a set of methods.

In my opinion, this is an understandable, but nevertheless futile path to follow.

If you want to reach a goal, a good strategy is always more fruitful, as it is open for change.

In software development we have a nice way to distinguishe between a method and a strategy. “Divide and Conquer” is an excellent example of a strategy, as it shows the difference to a method in that it does not says exactly in a repeatable manner, what one has to do, but a way of how things can be made solvable.

Methods are always bound to strict input parameters and therefore can be useful under certain circumstances.

But in order for a method to be effective, one has to ensure, that the proper circumstances are met. Otherwise all the effort is in vain.

Even if a method is the best possible one, it is always based on the concrete set of conditions.

So I’d say, that there is no such thing as the best method.