Years ago, I was a programmer. Although I was very poor at that time, I never despaired because I had no money, because I knew that there would be many days without money in the future.
After years of struggle, I finally became a technical manager and bought a car of my own.
I also understand one thing: people of my age must wear a safety helmet when riding an electric bike, otherwise, they will be recognized by the classmates driving a BMW Benz.
I remember when I was a technical manager, I still could not change the habit of pretending to be forced, and I often adopted some high and lofty management methodology.
I used to do everything I could to promote Agile, talking to the team, talking to the leader, talking to the boss. No, because if they don’t understand how good it is, who am I supposed to show it to?
Later I understand, load force even, if you load force also don’t admit, thunder will split you. Even if Ray doesn’t want to cut you, the boss will beat you up. Don’t ask me how I know that.
When it comes to agility, I have a unique perspective. I believe that as long as you work hard, there is no team that agile can’t break.
After all this, I am better able to talk about my own feelings.
1. Don’t believe in Agile
When it comes to Agile, employees think, “Stupid leader, there you go again!” “, “Agility is fast! Five men have done what ten men had done before! People are going to lose their jobs.”
When employees feel this way, you can feel free to be agile. Let employees push agility without understanding it and plant a time bomb.
As the saying goes, everything is difficult at the beginning, because the later difficult, you slowly get used to it. A good start and you’re halfway there.
2. Do not assign an Agile coach
Programmers are a bunch of super smart people. I’m a little bit worse. I’m just super smart. If you’re so smart, why do you need an Agile coach? Want to do training again, cut our leeks? It’s not that easy.
Everyone has a nine-year compulsory education, although I am a bit better than you: I went to school for ten years.
In fact, a lot of truth is “do not say”, agile is. Tuition fees still have to be paid, and it’s better to pay early than late.
Disrespect for team members
Remember, team members are not human and have no feelings. We should introduce agile, OKR and other advanced management tools into the team in batches, which will certainly cure the disease and greatly improve the combat effectiveness, no matter how the employees feel.
Do you know why the leaders at the top are all nice to the employees below, while the leaders at the bottom are all mean to their subordinates?
Let’s just say, have you ever seen someone angry about their office supplies?
No tolerance for mistakes
We are all working adults, the results are the talk, do not do well will be heavily punished, how can tolerate mistakes?
Why does Louis Vuitton produce so many bags every year if they can get away with making mistakes?
Five, avoid difficulties
Once Agile is implemented, the problem arises. Can temporary requirements be inserted? Do you need to write the document? Whether the project should be reviewed……
The first thing to do when you encounter problems is to calm down. Don’t worry what you can’t solve today, because you won’t be able to solve it tomorrow.
Make change an experiment
Isn’t Agile all about holding station meetings and drawing whiteboards? What is unusual, first look for a few teams to try, who knows the line ah?
Doesn’t Agile advocate “shoot first, aim later”? Let’s run first.
The question is, could it be an atomic bomb? If you disrupt the pace of your team and the normal conduct of your business, you may be in danger of losing your life.
7. Too radical
Agile is great, so many great companies are using Agile, we can’t even copy the homework?
All projects are switched to Agile mode, maturity L0 today, maturity L4 tomorrow. Only think, nothing can not do.
Remember the two laws:
- Agile is perfect;
- If you find any problems, please refer to # 1.
How could Agile be wrong? It must be our problem, we are not agile enough.
8. Criticize and attack the team
Why did man invent language? For the sake of gossip. All criticism and suggestions should be said in private, never on the table. The more mysterious the better.
What boss sister-in-law’s brother-in-law again with sister-in-law’s elder sister hit hot, which development elder brother secretly saw test sister in the crowd…… That point of old grain son rotten sesame matter, also want to divide ninety-nine eighty times to explain.
To let the atmosphere of the team, the destruction of the team’s great cause, it is not long before.
9. Intensify conflicts
The relationship between product and development, like the dou landowner, is a group of a moment ago, suddenly become enemies.
Sometimes like lovers, madly in love, lovers often lamented the previous life product what virtue; After getting married, couples often wonder what they have done in their previous lives.
Remember, development should never quarrel with the needs of the product, because after a whole morning of quarreling, the needs of others have been completely understood, where is your code?
Ten, lack of product planning
Since Agile, the product has completely taken off itself. When development is agile and capabilities are unleashed, what product planning is needed?
The world’s products, only copy can not break. Strong product managers are engaged in C2B —-Copy to BAT.
Copy Ali first, then copy Tencent, Baidu is not good, then copy a lot of it.
11. The technical architecture is out of control
Agile is so fast paced, how can we have time for technical architecture? All on the temporary plan, out of the problem on the patch, patch above again.
The accident on the line began to throw the pot, must be the problem of product design, or is not measured by the test, may be the problem of operation and maintenance……
In short, programmers should not put too much pressure on themselves and waste their hair. Not really, ready to delete the library and run.
Lack of tool support
Automated building tools are nothing new, and manual tools are no different, so polish them slowly and be a craftsman.
Don’t buy agile management tools. Excel is great. Wouldn’t it be nice to spend hundreds of thousands of dollars a year to give bonuses to your buddies?
Automated testing is also a loser. The tests are automated, so many cute test girls are laid off? Be a man.
You know, pretty test girls are the reason I go to work every day. Otherwise, what’s the difference between going to work and going to the grave.
13. Cultural divide
Let the culture of the team run its course, not the useless team building. What’s wrong with being a lone Wolf programmer? One good programmer can be better than 10 mediocre ones. They don’t have to fit in.
Also whole what unified shirt, team slogan, cultural wall? Kill me.
This is me, a different color of fireworks; I am who I am, and it annoys me to see myself.
conclusion
It’s not hard to bring down a team with Agile, and if you do half of the above 13 things, the team will probably collapse.
As the saying goes, not in charge of the family do not know the cost of daily necessities, do not take pictures do not know their own fat. Some things to keep trying, even if the car overturned, at least summed up the experience.
There are no shortcuts to Agile implementation, it’s all a step by step process. Experienced the wind and rain, not necessarily see the rainbow, but also may catch a bad cold.
But the dream still have to have, in case the ghost.
Source: Technical Leadership
Author: Mr. K
