How to develop and maintain fully-hosted Software

If we manage a software product, what aspects should we start?

We may be a team lead, a product manager, or a feature owner. No matter what role, I personally think that some aspects are particularly important.

Which of the following are listed one by one

 

• Function

Functions are certainly very important. No functional software. However, the more features you use, the better the performance. You must have a range. Create a do list based on this range and implement it one by one using the scrum method.

In this way, the boss and everyone are very clear about the progress and there will not be too much pressure on everyone. I have been a software engineer for several years. Many of my colleagues are also software engineers. Many of them are tired, but I seldom work overtime. I work less overtime because I have used this method in my company.

• Document

It's another fucking document, right. Everyone prefers to use documents, but almost everyone does not want to write documents. Why? I don't pay much attention to it. I think the code has been written, tested, and the work has been completed.

In view of this situation, I think it is necessary to improve the document status. The document is part of the work, and the work has not been completed yet. If you do not write a document, it is faster on the surface and saves time. However, you will pay more time for no document. For example, when a new person comes to communicate, he asks how much time it takes. If there is a document, he will directly throw it to him, you can just get started with "first look at the document. For another example, if there is no document, I forget it for a long time. For another example, if the product is large and many teams are developing and maintaining the product, communication between the team and the team will waste a lot of time if there is no document.

Of course, I am not saying that documents must be written at the beginning, and some things are indeed in a hurry. In this case, documents must be supplemented.

The document must be saved on sharepoint. Each member can see and download the document.

• Unit Test

No more time-saving than unit testing. After writing the code, you can see if there is any problem as soon as the unit test runs. Many people pay attention to unit test coverage, but do not forget test case, write enough test cases, and write unit test according to test case.