So far, I want to have been mixed in the IT industry for three years. During the reasons for the company project, I have done Delphi, Java, PDA, ASP.NET; although I don't know, but I'm not more and more What outcomes in the technical field, an accidental opportunity a year ago, I started to transfer business analysis, and the implementation plan planning of the entire system, I found that I did find my adaptive point, and what did you get a company colleague. Especially the truly recognition of customers! It feels particularly happy, although the process of doing demand is so annoying, but it is really challenging, requiring yourself with a particularly broad knowledge, just right for my character: fast learning ability is fast;
I summed up the death law of various IT staff:
The programmer is biting by bug (bug);
The tester is exhausted by the bug;
Business analysts are troubled;
The project manager is dead by all aspects of the personnel "rape".
Choosing BA, I am destined to die, today I repost an article, I have time I will write down my own experience and feel, I hope everyone will give me support!
Effective demand analyst
PMT Lev Reef May 2002
In the rest of the busy work, how do you become a demand analyst from an ordinary developer? Maybe just suddenly one day, your boss patted your shoulders, smiling and said to you: "The demand for this project is to do it!". After jealous, I can't help but have a little false. "Can I become an effective demand analyst?" Why is effective demand analysts that are difficult to produce, and the needs of demand analysis is correct, and completely affects the success or failure of the project, and demand analysts are direct responsible persons in demand analysis. However, our education, the working environment of our work constitutes us, making us difficult to become an effective demand analyst. In the university, the teachers will leave a few exercises for students, and these exercises are almost not thinking, they can know what it requires. It is not necessary to analyze the demand analysis. Don't consider how to make effective Demand analysis. However, these students, after graduation, they need to face intricate, frequent changes, need to discover demand like experts, excavate demand, but these "soldiers" have not been well trained, they can win this. Does the "battle" of the game? Most of the needs analysts have grown from developers. In the work, we didn't send it for a long time. He faced the cold display, the finger flew on the keyboard, with a mysterious smile, what is written in a strange symbol. We live in a digital world, and many people may never come into contact with any customer. However, one day, we found that he had to face a large group of users, even worse, these people didn't understand what is C , and I have never heard of the Internet. "Heaven, what can I talk to them?" There is such a paradox now, thinking that excellent programmers will also be a valid needs analyst, but our education, our work does not teach us how we do Become an effective demand analyst. Just like encoding, testing, project management, there is a lot of techniques in demand analysis. It's hard to imagine that you can master a programming language without tough training, and the demand analysis is also the same. However, in reality, many programmers have become a demand analyst, which has become a need for analysts lack sufficient technique. What is a valid demand analyst? A effective demand analyst needs to establish a real partnership in work and users in the demand analysis process, which can find problems behind the problem in an intricate phenomenon, can learn in a strange field. Faster, but also to communicate with common language and users in work and users build real partnerships. And users build a real partnership we know what the user's business goal is? We know what the user's three-year-old development policy is? Do we know which benefits can our software bring to users? Do users treat us as friends? And user-building partnerships are often written on paper, not in their hearts, more implementation in practical actions. And the user-building partnership is not an empty slogan, but is responsible for the user's business results. It is not a good wish of itching, but requires the intensive unity, the exchange of useful information and cooperative results. As a demand analyst, we ask yourself, do you really put the user's business goal first in the demand analysis? Do you really think users as our partner? Do not understand the goals of users, do not respect the user's interests, can we analyze the needs of users surprises? Can you develop a lot of value for users? How can I establish a real partnership with users? First, to transform our attitude.
Many IT people are self-interested as "social elites", "high-tech talents", in the process of communicating with users, especially traditional industries, almost habitual arrogance. What will the user feel? If the demand analyst works with such an attitude? Is our service to users, or teach users? How can we do "think like users" with great attitude towards Therefore, we must change your attitude, and sincerely treat the user as God as God. To understand, it is the user's money to support us. Second, cultivate interpersonal relationships. Demand analysis is not a transaction. It is not a hammer who will be able to buy and sell the money. We must sincerely face our customers, with sincere exchange, try our best to become friends. Third, we must start our business imagination. Bold to seek better ways to meet user needs. Like a user, thinking is far less than enough, we have to see more clear, that is, the "surpass users" often said. Issues behind the problem Behind the start of a software project, the user's demand is often developing software that completes a feature (such as personnel management, finance, etc.) to solve the current problems. But what is the value that the software really creates the user, this is a problem that every demand analyst must think. Demand analysis should be a systematic thinking, a requirement to "see trees and see Lin" work. Effective demand analysts want to look into a system and integrate it into this large system, comprehensive observation of the user's work, not a fragment, a piece of an individual event. For example, users need to develop a personnel management software, the demand on the surface may be more convenient to manage employees, but substantially demand may be solved by personnel management software to solve the work discipline, attendance is not strict, and the personnel flow will be free. Similarly, users need to develop a financial software, in addition to better management funds, their real purpose may be to solve the problem of confusion in the internal financial system. If the demand analysis is just the problem of staying on the surface, it is difficult to discover the problem that the user is really concerned, it is difficult to believe that the developed software will allow the user to be satisfied from the heart. If you find the problem behind the problem? In most companies, in addition to some formal organizations, there are also various informal organizations, which requires demand analysts in the process of demand analysis, in addition to using official channels (conference, interviews, etc.) It is also good at using informal channels (talk in lunch, private talks, etc.) to understand the needs of users. We will find that informal channels are often the key to the problem behind the problem. In addition, we need to master an effective analysis method - "deep farm law". Here is an example of a deep cultivation: Problem Cause This morning, a motor bed is closed. Why is the seal of the seal of the machine? Because the seal quality of the purchasing is unqualified why is the sealed seal? Because the price is 10% why is such a small difference? Because the performance of the procurement person is based on the purchasing. Therefore, the matter is the basis of the problem to change the performance evaluation criteria for the purchaser!
Through a series of "why?", We can find the problem behind the problem. "What is the truly need of the user?", Each requirement analyst should constantly ask yourself in the process of demanding analysis, to remember a fact, "things tend to be more complicated than it." Only the real integration into the user, becoming a member of the user group, in order to find the problem behind the problem, in order to make a product that truly satisfied with the user. Differential incorrect demand has become the largest culprit leading to software development failure, especially software applied to the non-mechanical industry. Demand analysts are often not an industry expert. In the demand analysis of ten and a half months, it is difficult to fully understand an industry expert with more than ten years of experience. This is a very brutal reality and a fact that we must face. It is because understanding the one-sided and deviation of the understanding result in many software projects to take a tragic ending. An effective demand analyst should be a person who is good at learning. Only by learning faster can make a demand analyst to become a "hipster hand" in a short demand analysis stage, thinking about thinking, action like an industry expert. However, learning ability is not to improve, and demand analysts must continue to strengthen their daily work learning, and learn from faster speed as much as possible. As long as you persistent, you will have a big gain. An effective demand analyst should also be happy to learn. When he faces a new industry, he can use the imaginary enthusiasm and speed to learn, understand, to integrate, not excluding, disgusted, and even curse. Many IT people have a bad idea that there is a sense of rejection of the traditional industry. This exclusion is often caused by the needs of analysts and users, and the results can I know . Communication with common languages When IBM AS400 is released, IBM has identified an expert in a numerous expert in many experts, and it is easy to understand the expert, the technical term "translation". This expert speaking all the advantages of AS400 in the conference, all reporters in the scene can be easily understood, making the release of unprecedented success. As a demand analyst, the technology should be quite understanding, but we can't expect that our users can also have the same deep understanding of IT technology as we have. Users may not know what is "component", what is "object-oriented", even unclear "10M bandwidth network and 100M bandwidth network." For users, they are more familiar with the terms and standards of their industry. So the strange phenomenon, users and demand analysts communicate with each other, it is like a Chinese and a French who have their own mother tongues in communication, maybe more chaotic, not consensus. In this case, can we expect accurate and comprehensive user needs? How should an effective demand analyst solve this problem? First, you should work hard to familiarize yourself with the user's industry, learn the terms, standards used by users, so that users can be able to understand users. This requires us to read the information, articles in the industry in which users are located, and as much as possible to select some articles introduced in the industry, so that there is a comprehensive understanding of the industry in a short time, so we can better and users. Communicate. Second, we should do not use the terminology of the IT industry, and use the verbal language of the IT industry to explain the highly murisable terms in the IT industry so that users can understand well. We can explain to the user 10M bandwidth network and 100M bandwidth network What is the difference: "10M bandwidth network is like a dual-lane asphalt road, easy to traffic, and 100M bandwidth network is a highway of 20 lanes, traffic jams. The possibility is very small. " Such explanation users can understand well. However, explaining the terminology of the IT industry with a flat language is not an easy task.
