Powers we lost

The situation with which I often come across forced me to talk about the powers of the development team and in particular about their use. Modern flexible areas of development (in particular Scrum) provide ample opportunities for self-organization. Methodology consultants train managers around the world to give teams full technical decision-making and freedom of action. And I must admit that many of our leaders really succeed in this. First with caution, and then more and more aggressively offer their teams additional powers and support.

Are all teams ready to accept these new, I would say unprecedented powers? Unfortunately, not all. Most of them do not even realize all the opportunities that are in their hands.

I would like to recall these powers. The powers that are used by self-organized teams of professionals, teams that do the real thing. Teams that do not ask for permission to refactor do not ask for permission to write a test. Because such things are part of the life of professionals. They have the authority to do their job well and enjoy it without apologizing for being professional. Such teams are motivated because they want to be so. Because they are not indifferent. They sincerely, deeply worry about what they create. And I think it should be. This is the very first, right step on the road to success. If you really care about your profession, you need to learn how to use the powers you have. Powers to develop a really cool product, to write clear and high-quality code. You need to think very seriously about this. It is for you. This will allow you to feel pride in what you are doing, change your attitude towards yourself, change your company ... The ball is on your side. It's up to you.
')
PS I give a link to the original article, which I essentially changed.