How to effectively implement software demand management-7

[This article is article 7 on how to effectively implement software demand management ,(Article 1,Article 2,Article 3,Article 4,Article 5, Article 6, Article 7, Article 8 )]

 

 

After obtaining a requirement from our company,

First, the relevant personnel will firstDevspecCreate an entry and add relevant property information, such as title, content description, status, corresponding document, priority, urgency, owner, corresponding version, corresponding browser, corresponding database...

 

 

 

After the entry is submitted, a person in charge is set for this entry, so the person in charge can log on to the system and immediately see the entry under his/her name. Then, he will immediately handle this requirement. (Some users may not log on to the system. We can also set the automatic email or SMS reminder function)

 

The "owner" mentioned here is different in different processes. For example, there is a special reviewer in the "Review" stage, and ordinary people cannot become reviewers, persons who can become owners can be set in the process. After you submit an entry, the first process is to review the requirement you just obtained, after the approval, the owner can change the requirement from the "Review" status to the "requirement analysis" stage. Of course, the owner will change, the person in charge of the "Demand Analysis" process will immediately know that he has something to do.

 

In this way, after a process, the person in charge is handled one by one, and the demand gradually changes from an idea to an outline, and then designs the framework, then it is implemented.

 

The difference is that we use a tool to manage the process. Some companies only need to do it manually. The advantages and disadvantages of doing so are actually there. As a customer asked before, will the processing efficiency of every requirement be reduced if you do so? Yes, it will indeed decrease. We admit that, because these are strict procedures and are managed in a system, it is certainly not as fast as they speak. However, we are considering selling products and sacrificing some efficiency to ensure product quality. We feel that quality is the most important thing after all. Although people are doing fast, there are also many problems. When there are many demands, there are more things to forget to do, the wrong thing, or the mutual responsibility to push, problems with product quality are everywhere. However, after using the system, we have avoided these things. Practice also proves that after we do so, the product quality is guaranteed.

 

Of course, the quality of the product is not simply as I said above, "after one process, one by one person in charge" can be achieved immediately, I will pay attention to a lot of details here.

 

I have said before that there are several strict requirements for demand management. As you can see in the process and review mechanisms, in fact, to some extent, review is part of the process, because the review process itself is a process in the Process of requirement processing, we only need to set this process in the process and arrange the owner to be responsible. When the requirement enters this process, someone will review it.

 

If we regard the above two requirements as the basis of requirement management, there are several other strict requirements:Welcome to change, version control, and trackabilityTo ensure the success of the product quality.With the foundation, you can succeed. With the key points, you can ensure success!

 

Welcome to change:

 

Welcome to the importance of changes. You should know that a change is actually a change in demand. To some extent, it means that the quality of the product is declining, because this demand is constantly changing, I have just written this code today. I want to change it like that tomorrow, and I want to make major changes the day after tomorrow. Who knows there are potential risks and there are also functions associated with it? You suddenly changed an interface parameter, which may not be known yet. Test? The Tester could not solve this problem well, because the tester just finished testing this function today and changed it tomorrow. However, although the tester saw that this function needs to be tested, however, he may think that the test has been completed yesterday, and does not forget to disable it, so he will test other functions.

 

How can this problem be solved??It is also very simple. When there is a change,

 

First, try to let the relevant people know, let the development know, let the test know, let the people who need our interface know, so that everyone will complete what they want to do in sync, there will be no need for the person to do but not know that he is going to do this. InDevspec, We can useAutomatic notification of changesInDevspecA requirement is always associated with its development and test tasks. Therefore, when a requirement changes, you only need to send a notification, developers and testers can immediately see the changes and do their work in a timely manner.

 

The second is to try to clarify the scope of the impact so that developers can know where the impact may be, and be careful when doing so; let the test know where potential bugs will be caused by this change, and focus on the tests. InDevspecIn, we will have a special function for designers and developers to indicate the impact of the place, need to focus on the test, and this function can be set to mandatory, as long as there is a change, designers and developers must specify, or even testers can be asked to specify the points to be tested, so that design and developers can check for any omissions.

 

The third point is that for any change (especially for companies like the waterfall model), the relationship may affect the quality, progress, and cost, which is highly risky, therefore, a special review process is required for the change content. Development can only begin after the review is passed. InDevspec.Change management viewIn this view, there will be a special process to review changes. During this period, this requirement cannot be transferred to the development stage by anyone, and some people may not be clear about the situation, directly let the developers do the unreviewed requirements. (Of course, many of our products are now in Agile development mode, so this function is rarely used)

 

 

In this way, we can still put quality in our own hands, that is, to put the future of the company in our own hands.

 

 

 

(To be continued)