One thousand and one Q & A Series 3 in Agile development: Preface and question-solving (resonance)

This is the third article in the Q & A series of agile development one thousand and one. (Here, I would like to ask, one, two, three, and the General Directory of the question)

It is also the first article in The Prajna agile series. (One, two, three, four, five, six, seven, eight, nine, ten, eleven, twelve)

Resonance

Resonance is a concrete practice of promoting agility without me or spirit.

It is easy to be understood as step-by-step, but this is not comprehensive, which is why the strange word "resonance" appears. It is difficult to find a complete alternative word or statement without ambiguity.

Step by step

Many people dream of a company with the support of senior leaders. The company culture is suitable. The team members have strong personal abilities and can cooperate smoothly, so they only need to promote Agility by their project managers. But with an eye open, my company is not like this. Therefore, "our actual company is not suitable for agile promotion ".

In many cases, organizational architecture, product features, and personnel capabilities all affect promotion agility (these will all appear in question one thousand and one), but this will only affect "The best way to achieve it ", this does not affect "Better implementation ". People who lie in the slave society without being able to realize communism are actually the least agile.

Step by step, it is a concrete practice to promote agility without a spirit.

In the eyes of people who have mastered resonance,This is not a company that "some agile practices cannot be carried out", but a company that "some agile practices can be carried out ".

Persuade, help, and do things for others

There is another situation, such as "our project team has learned agile development methods, but the product manager does not write user stories. What should I do ?" Even more tricky: "The first point of product priority sorting is to sort products by business plan, but our company has no product director and never has a business plan. What should we do ?" (These will all appear in question one thousand and one)

In every silence crowd event, when I pull out an interview from anyone alone, he will say, "Actually, I wanted to help, but I saw so many people choose silence, I also had to silence myself."

In fact, we can't think of ourselves as superior, but we are falling into the pile of fanfu, and we can't do anything with it. "Most of these people share the same idea with me, but they either lack a specific approach or a lack of one ."

So when we find that the product manager does not write user stories, we can try to persuade him to do this well. Maybe he is worried about how to write the story, so he is hesitant, we should help him write well together. He has written user stories, and our development will be smoother. If he is confused and refuses to help, we will do well for him.

Do not think that you have suffered losses for helping people to do things or for others.

We had a tester who just transferred to the Technical Support Department. Everyone thought that "writing a solution" was a task and pushed it to her; later, I said that the word version solution could not be described, so please change it to a PPT. Later I suggested that I am not familiar with the solution, so I would like to ask you directly ...... One year later, the company's policy adjusted sales competition for posts. In half a year, she opened the situation in a brand new field (that is, the area covered by the solution) and made a deal with one of the largest orders in the company's history, and became the new sales champion, with an increase of 200% in revenue.

To persuade, help, and do things for others is to promote agile practices without my mind.

In the eyes of people who have mastered resonance,This is not a company where "some people cannot work with me", but a company where "I can work with some people ".

Break old me and create new me

The scope of "Others" is not only the outer and upper layers that we cannot control, but also our team members and masters.

In my mind, there is no such thing as a "should be dismissed", but only "players who are talented and cannot make full use of the skills they should help". If there is no "will starve my apprentice to death after learning ", however, there is only "brother who will take over my work to allow me to manage more tasks", and there is no "other departments that refuse to do their jobs ", only "other departments that may be assisted, replaced, or managed by my subordinates ".

Break away from the old ones"New me" is not a specific position, but a higher and better direction, specifically "No Me". Otherwise, your career will stop at a certain position.

Bill Gates, programmers of those years, have been able to span so many positions in a short period of time. One necessary condition is that they never stick to "I am a programmer, so I should not care ......", I believe that everything is what I want to do. I can become anyone.

Although this is not a sufficient condition for success, it will never succeed without this amount of heart.

The above three articles are the core methods to solve all known and unknown problems. If you master these problems, you will not be confused or afraid, it doesn't just pin your hopes on a master's ability to answer this question, but to analyze and solve it by yourself.

Subsequent problems and analysis are based on the above three aspects. Maybe we can still summarize the Fourth word in the future, but now only the words "no", "no", and "resonance" are enough.