How to effectively implement software requirement management-6

[This is the sixth article 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 the demand analysis stage is complete, it is the demand design, and then the demand implementation. The process looks simple, but the actual work is not simple, the strict requirements of demand management mentioned above have been the beginning and end of the entire process.

 

Next, I will introduce the actual implementation of demand management based on the actual process of our company.

 

If I have read my previous articles, I should know the background of our company. Our company is also engaged in software development, so it also attaches great importance to demand management. We use agile models to manage the entire software development, so the demand management stage is also in line with agile models, but the strict requirements for demand management are also basically observed.

 

Our company usesTechexcelRequirement management toolsDevspecTo manage the entire demand process, we actually bought their complete software lifecycle management solution calledDevsuite, AndDevspecIs one of the tools that can be usedDevsuiteOther tools of the solution are seamlessly integrated to help you manage development, testing, planning, and other stages.

 

 

 

 

 

 

 

 

InDevspecIn, demand management is managed by means of entry. The so-called entry-based means that a requirement is an entry, which includesRequirement Description, IncludingTracking of demand handling process:

 

• For the Requirement Description,DevspecIt is implemented through attribute fields. You can use fields to describe the requirements as practically as possible, including basic fields such as title, status, owner, description, time, and attachment, of course, you can also customize a large number of attribute fields and pages to better describe this requirement.

 

 

 

• For the processing of requirements,

We know that there is a process to process the requirements. simply, we need to review the requirements from requirement analysis> requirement design> requirement implementation, just like the flowchart I showed you above, I will post it here.

 

 

 

 

 

However, it is useless to simply have a process. I believe that any company will have a process to deal with its needs, but it is not strictly or seriously different. There is a very high possibility that it will not succeed if it does not follow the process, so to solve this problem,DevspecSpecifically, you can design customizable workflows. You can define the processes required for development. Once the process is defined, the demand processing will be forced to follow the process, and you can't do it if you want to be sloppy and relaxed.

 

In the process,DevspecDifferent owners and permissions can be set for each process. For example, this process is handled by Mr. Smith. Therefore, only Mr. Smith can see this requirement and handle it. Other people cannot see this requirement if they do not have the permission; after Mr. Wang finishes his work, he may not have the right to turn the demand to the next process, because another person needs to review it before continuing.

 

In this case,

 

First, yourProcessIt will be very clear, this step is complete, what is the next step, it is clear;

 

Second, yourManagement ProcessIt is also very transparent. Who will handle it now and who will handle it.

 

Third, yourPower ProcessIt is also quite clear that people at any level can set what they can do, what they should do and what they should not read, this prevents some people from seeing what they shouldn't see and doing what they shouldn't.

 

With these attributes and procedures, we can officially startDevspecRequirements are managed.

 

 

(To be continued)