"Sulfuric" beekeeping or the game of humanism
Let’s think, who needs humane development methodologies? Team, responsibility, courage, trust ...
The investor doesn’t give a damn what software process is being used. He needs profit, as much as possible and faster. And money, as you know, does not smell. He wants the invested penny paid off.
If things don’t work, he will sell the whole company with the team, giblets and processes to the one who pays the most. And let everyone be fired in the company after that, he doesn’t care.
He needs the project:
a) to be fairly accurately described, agreed with the customer and the requirements not changed. Then it is easy to evaluate, plan the stages of work and perform the waterfall.
b) What kind of relationship does the development team — the agile there or the Gestapo with daily dismemberments — give a damn about. There should be progress on the project, stages must be completed on time.
Then the manager can stutter about the salary increase, hint to the boss about career growth. As soon as the opportunity arises to leave for a highly paid prestigious job, he will do it because the future leader subconsciously fights for power and looks up.
These guys dream that the Customer together with the project manager (cross out the necessary) do not change the requirements, or do it rarely - because It is difficult and expensive to make changes to the written and tested code in the middle of the process.
Colleagues do not want specialists - developers, layout designers, designers, testers - to be easily lured by offering 5 tr. more. To this end, employees will be given a dosed play of new technologies so that they feel their involvement in the beautiful.
If processes are not delivered, project documentation is not kept, that is, there is a risk that a leader will appear in the team who will lead her to another company. In this case, the above colleagues will probably be fired. Therefore, the search and shooting through the dismissal / substitution of such potential competitors.
Perhaps only in this case, the development management will need an edge, as a competitive advantage - we have a humane process, a team, and if you leave the company as a friend, you will be blacks and IT plumbers.
However, if the process is set, everything is documented, ISO / CMM or sustainable business processes - then for the sake of increasing efficiency you can fire people and change them like gloves, for any deviation - projects will not stop, new business process employees will quickly take courses and take place of the departed. Those. humanity is no longer needed.
A person wants comfort at work, communication with colleagues, especially women (active communication). I want to avoid personal responsibility (the whole team is responsible for everything). Go to work and hang out. I would like to choose which tasks to do and which not to evaluate myself (Planning Poker).
And the leader (Scrum-master) is generally Jesus Christ with the staff - a mentor, does not fight, does not swear at obscenities, only teaches and develops. Paradise on earth!
This is where humane development methodologies fit perfectly :-).
But. If a specialist wants to grow into a development manager, technical expert, project manager - he and the team and the atmosphere of the hangout are no longer on the way. He is the sole person. He is a future leader / expert. Therefore, he will stand out among others, even humiliate them to enhance contrast. Whether he will become a manager in this humane company is unlikely, but in another ... why not.
Sometimes IT managers come across who perceive flexible methodologies as a means of squeezing out all juices from engineering teams. Scheduled sex several times a day. Still - daily planning meetings, open space - a specialist cannot fall for a couple of days, live on forums, read technology news. Stand-ups, intensive assaults on tasks, pair programming, demonstrations. People in the team are quickly aging, the nervous system is destroyed by the effect of life behind glass - but projects are moving forward, features are being done.
And here we come to the topic of "sulfur" beekeeping :-). When breeding bees there are roughly two strategies - humane and cruel.
When humane - the bee family after harvesting honey in the summer is left for the winter and until the next season. At the same time, for the bees to winter, they are left 10-20 kilograms of honey for food.
In a violent - bee family after harvesting ... poisoned with sulfur. Why? They do not need to leave tens of kilograms of honey for the winter, but it can be sold. And with the money they make, they buy a new family in the spring, and so on :-)
And they often do this to people - they catch up with a bunch of programmers, treat them like cattle, they write a bunch of shit, then they fire especially smart ones and just to have fun, they hire new ones again and so on.
Yes, we, as experts, understand what kind of system will be born in such an inhuman process that the house of brain tolerance will be a code that the system in convulsions will collapse in a couple of years.
How can we convey to the “powerful people of this world” that just to make a profit it is necessary first of all to enable people in the team to open up, realize themselves, not leave the company for 5-10 years, be proud of their projects, their code?
Or is it a communist utopia and a struggle for the freedom of programmers? So who benefits from humane methodologies? :-)
Investor
The investor doesn’t give a damn what software process is being used. He needs profit, as much as possible and faster. And money, as you know, does not smell. He wants the invested penny paid off.
If things don’t work, he will sell the whole company with the team, giblets and processes to the one who pays the most. And let everyone be fired in the company after that, he doesn’t care.
Project manager
He needs the project:
a) to be fairly accurately described, agreed with the customer and the requirements not changed. Then it is easy to evaluate, plan the stages of work and perform the waterfall.
b) What kind of relationship does the development team — the agile there or the Gestapo with daily dismemberments — give a damn about. There should be progress on the project, stages must be completed on time.
Then the manager can stutter about the salary increase, hint to the boss about career growth. As soon as the opportunity arises to leave for a highly paid prestigious job, he will do it because the future leader subconsciously fights for power and looks up.
Development manager
These guys dream that the Customer together with the project manager (cross out the necessary) do not change the requirements, or do it rarely - because It is difficult and expensive to make changes to the written and tested code in the middle of the process.
Colleagues do not want specialists - developers, layout designers, designers, testers - to be easily lured by offering 5 tr. more. To this end, employees will be given a dosed play of new technologies so that they feel their involvement in the beautiful.
If processes are not delivered, project documentation is not kept, that is, there is a risk that a leader will appear in the team who will lead her to another company. In this case, the above colleagues will probably be fired. Therefore, the search and shooting through the dismissal / substitution of such potential competitors.
Perhaps only in this case, the development management will need an edge, as a competitive advantage - we have a humane process, a team, and if you leave the company as a friend, you will be blacks and IT plumbers.
However, if the process is set, everything is documented, ISO / CMM or sustainable business processes - then for the sake of increasing efficiency you can fire people and change them like gloves, for any deviation - projects will not stop, new business process employees will quickly take courses and take place of the departed. Those. humanity is no longer needed.
Specialist (developer, etc.)
A person wants comfort at work, communication with colleagues, especially women (active communication). I want to avoid personal responsibility (the whole team is responsible for everything). Go to work and hang out. I would like to choose which tasks to do and which not to evaluate myself (Planning Poker).
And the leader (Scrum-master) is generally Jesus Christ with the staff - a mentor, does not fight, does not swear at obscenities, only teaches and develops. Paradise on earth!
This is where humane development methodologies fit perfectly :-).
But. If a specialist wants to grow into a development manager, technical expert, project manager - he and the team and the atmosphere of the hangout are no longer on the way. He is the sole person. He is a future leader / expert. Therefore, he will stand out among others, even humiliate them to enhance contrast. Whether he will become a manager in this humane company is unlikely, but in another ... why not.
Gestapo Edge
Sometimes IT managers come across who perceive flexible methodologies as a means of squeezing out all juices from engineering teams. Scheduled sex several times a day. Still - daily planning meetings, open space - a specialist cannot fall for a couple of days, live on forums, read technology news. Stand-ups, intensive assaults on tasks, pair programming, demonstrations. People in the team are quickly aging, the nervous system is destroyed by the effect of life behind glass - but projects are moving forward, features are being done.
And here we come to the topic of "sulfur" beekeeping :-). When breeding bees there are roughly two strategies - humane and cruel.
When humane - the bee family after harvesting honey in the summer is left for the winter and until the next season. At the same time, for the bees to winter, they are left 10-20 kilograms of honey for food.
In a violent - bee family after harvesting ... poisoned with sulfur. Why? They do not need to leave tens of kilograms of honey for the winter, but it can be sold. And with the money they make, they buy a new family in the spring, and so on :-)
And they often do this to people - they catch up with a bunch of programmers, treat them like cattle, they write a bunch of shit, then they fire especially smart ones and just to have fun, they hire new ones again and so on.
Yes, we, as experts, understand what kind of system will be born in such an inhuman process that the house of brain tolerance will be a code that the system in convulsions will collapse in a couple of years.
How can we convey to the “powerful people of this world” that just to make a profit it is necessary first of all to enable people in the team to open up, realize themselves, not leave the company for 5-10 years, be proud of their projects, their code?
Or is it a communist utopia and a struggle for the freedom of programmers? So who benefits from humane methodologies? :-)
