Agile development with tools-7

However, as a result, the problem arises. Although we can manage the basic attributes of a function point in this way, in actual work, our work is often not so simple, because according to past experience, there are a series of problems that need to be solved in the process from thinking to designing documents. If one problem is not solved well, this function may fail. At the time of training, we also listed these issues, but devspec was indeed very powerful and basically met our needs. Next I will list several major problems and their solutions:

1. Multiple changes to the function:

We know that it is a very long process from having a concept in our mind to final finalization to development. It will be constantly changed, so there is a very likely thing to happen, that is, I think this idea is good today, but tomorrow I think that idea is good, but I still think that idea is good on the first day of the day. Even after a week of change, I think that idea is good a week ago. However, the problem is that every time I change it, I have saved it to the requirement task, covering the original description. So how can I find the original description? Do you want to press Ctrl + Z like Microsoft Word? After you restart your computer many times, you cannot press Ctrl + Z for word, after you change your computer, word doesn't know what you want to recover. Fortunately, devspec has a function, that is, each change will save a copy, just like the Subversion we use during programming. A new version will be added once, this means that any changes you have made before are made and can be seen. With another rollback function, you can overwrite the original ideas into the latest version. This completely solves the problem of data loss.

2. problems that need to be modified again after the function points are completed:

We know that agile development emphasizes feature changes. That is to say, during product development, you are welcome to change features anytime and anywhere. Any new ideas you may have can be implemented. However, a problem arises. When a feature is being done but is not completed or even completed, the customer says that I need to add or change a feature, then the design team completed the design. How can we get the fastest time for development or testing to know the change, so that we can immediately prepare for re-development and re-test? Techexcel provides us with another function, namely the change notification function. Once a function is changed again, the designer can enable the notification function, developers or testers will see a small red flag in the development tasks and test tasks corresponding to this function point. As long as they see this flag, developers and testers will know that something has changed, I may have to repeat the design document and test or develop it again. Maybe you can send a notification by phone or email. I can, but the problem arises again. Even though the phone and email can notify people, but once that person forgets this, it will be miserable, and the devspec reminder feature will always show that it will not disappear until developers or testers finish what they should do.

3. Keep abreast of development and testing progress issues:

After a function is developed and tested, the product manager and project manager need to test it to verify whether the function fully meets the requirements of the customer. How can I know that this function has been developed or tested? Yes, you can. But if this function is implemented by five developers, do you ask each other one by one, and the time for their completion will also come successively, you do not know which part of this development is used. How can we implement devspec? First, after the function point is designed, we will use this function point to generate development and test tasks, all the generated development tasks and test tasks are linked to the task of this function point, that is, on a page of the Function Point, you can see the status and owner of all development and test tasks linked to it. In this case, our product manager and project manager can find the information they want to view on this page. Then, when a function is developed by five developers, when a development task is generated by this function, we can directly select different tasks for different parts and assign different owners, in this way, a task is generated for each of the five developers, and these five tasks are linked to this function point.

 

The above are some of the major issues we have mentioned to help solve. Of course, there are other features we advocate that we will not discuss in detail for the moment. Let's take a look at them:

1. Voting function: Everyone can vote to decide whether to do this function or whether this function is good or not.

2. Cost statistics: analyze the telephone bill time and resources

3. Install the plug-in the office. You can directly convert the document into a requirement or several requirement tasks in devspec, or convert the PDF file into a requirement (which I like)

4. Right-click the plug-in to add all files in the computer to devspec as an entry without opening devspec. (I like it too)

5. Of course, the report function is also indispensable. devspec provides many useful reports.

6. the automatic reminder function. For example, if you have a request, an email will automatically remind you, or if you have a requirement that is always under your name, but you have never handled it, you will receive an email to remind you later.