About (flexible) methodologies

I do not belong to the camp of supporters or opponents of a particular methodology. It is a tool that works wonders in capable hands, and does not work wonders in inept ones. Earlier, I already wrote a little about trends elevated to a cult , in the list of which flexible methodologies (in common language - Edzheel), in my opinion, occupy an important place. In this article we will briefly go through the main points of using methodologies, including flexible ones.



There are no bad and good methodologies. There are suitable and not suitable.
')
If you have any doubts, what methodology should be used in a particular situation and in a specific project - it is better not to use it at all. So you minimize the risks of improper implementation and save time on the implementation itself.

Before introducing a methodology, you need to make a list of reasons why this methodology will not work. In the secular world, this is called “risk assessment.”

All debates about whether documentation is needed or not, whether PM is needed or not, etc. meaningless without consideration of a specific team / customer / conditions.

In agile methodologies, there is one very significant drawback - collective responsibility (that is, its complete absence in practice).

If successful, we can say that all this was possible only thanks to the methodology. In the case of the Fail, in principle, it can also be said that this “just the methodology was somehow implemented for the moronic”. For example, the skram board was mistakenly hung in the west, but it was necessary in the east.

There are practically no “clean” implementations of any methodologies in real life.

Agile is like HTML5 on mobile phones. In words, cool, but all pedal native applications.

It is believed that those who do not like agile - just do not know how to cook it (implement). OK.

Two of the most epic implementations of scram in my practice: 1) implementation in a research & development project (R & D is when any assessment of the task is inaccurate a little more than completely) in a team of one person 2) introduction of scram in a team that has not yet been recruited. In both cases, the projects ended with an epic file.

Do I need to learn different methodologies? - Yes. Does one methodology need to be applied? - Not.

Agile is a manifesto that consists of tips and best practices. In practice, each team should have its own set of rules and best practices that work for them and may not work for everyone else.

Methodologies are nothing, people are everything.

Well, as the completion of a joke in the subject: - Hello! Copy me your company. - What!? - Oh, sorry, I didn’t start from that. Do you use Agile?

Thanks for attention!