Our project team has mainly developed a terminal product, with this product to form a communication platform, which can do a lot of applications on this communication platform. Our products have been bought from a foreign company. It is called BET. This product is still more advanced. Although there are also some manufacturers to produce, it is generally in the form of semi-finished product, and we can get the evaluation circuit and most source code, do some specialized applications. The entire project lasted for 3 years, I joined when I was transferred to half, and I didn't see the successful business of the project. Summarizing, I feel a lot lesson.
And program suppliers are not communicating
There are many bugs in the source code provided by BET. We also reflected many questions during the development process, but they have not been resolved. On the contrary, BET only keeps chasing our payment (technical support cost OR Solving Program costs), there is approolby of 6-7 months, in technical support and BET company has been entangled, and no form of technical support is obtained. I remember that in the end, Bet Company and our emails were about money - do not give it, requiring first resolution of these stalemates. Later, the product is almost completed, BUG I don't know why, I don't know how I will.
I can't easily push it on some side, maybe because both parties communicate.
The plan is disorderly, exhausted, I have never understood today, when is the product of our project group mature. At the end of last year and after this year's Spring Festival, I became very busy. Because at this time, the product will give the customer to the customer, at that time, the overtime of Dan Dan, suffering. I used to be a job that I am running, but I will start to lose interest in my work. I don't think that the entire project group does not seem to have an evolution plan, and the products have not been in a mature stage. Every time they are customers say, I want this feature, and then began to add this function. There is no more clear goal for the product.
Later, I chatted with another colleague. He believed that in the later stage of the project, there were many customers who came inquired, and there were no cases in success. In the final analysis, leaders generally don't want to invest in a more mature product, but a lot of relying on the hand is not a very mature product, I can talk about a order first, this is actually a common disease, the company does not correspond Incentive mechanism, can't see the prospect, the average people are not willing to invest, this is far away.
The great person is wasted about 35 people, divided into two groups into two groups into hardware, software, and hardware parts. There are about 14 people, and the software part is divided into three groups, with a total of 23 people. There are 2 groups. Around 14 people, they first do two of the prospective sub-projects RP and RW, in the communication market at home and abroad, these two sub-projects themselves are very large, many companies are invested in hundreds and Very large material for research. And I haven't seen these two sub-projects have a large-scale commercial need. I don't know what purpose in this project group launched these two subprojects. Finally, the "prototype" of these two subprojects is made. Just 1 pure demonstration, running on the PC, getting from the real hardware platform, developers do not have a good face outside the programming language and agreement, another I have never seen its true face, it is also related to the practicality, doing It's equal to nothing, just familiar with the BET scheme, without any practical use.
Later, I repeatedly find the reason for these two subprojects, I think this may be caused by the mechanism of the entire company and the project group. First of all, it is a pre-studied project. Is there no market pressure at the beginning of the start? So the two subprojects will be launched? However, this reason is very insufficient. The product positioning is not clear, and the new idea project team with an emerged end has been more than 1 year. At the beginning, we have done a specific product, a specific communication platform. Later, I feel that this market is very limited, so I turn this communication. The application on the platform, transferred from the specific platform to the application on this platform, and then, it is the problem of system integration, but also sells the relevant software system and various chaos 78 mess. . In fact, the software system running on the PC has only one person, and the professional companies have a certain gap in some respects. When discussing with customers, I said that this system is currently used, we mainly sell the communication platform, and I will say again, of course, we can do a complete set of systems (as long as there is order ...) to the end, we I started to take the development tool on this communication platform as a selling point, toss it, still didn't get orders.
With a market manager who accompany the project group manager and the competent product, he said that some difficult to listen is really practical. I don't care what you can do, I know what you can do, the problem is that you have to take things. Come out, then I can sell ...
The words come back, unless the experience is very rich project manager, has the experience of all aspects of hardware and software, but also to understand the industry, market, otherwise, it is difficult to make a conclusion of product positioning, and market positioning is often Constantly evolved in practice. Leaders must do their best to make the situation that may arise, and have a number in mind.
Problems in development
Once, we cooperated with a company in the field to develop an app. After completing this application, I tested this system again and found that the other party's agreement has changed. I turned to ask a interface in Team. He said that the agreement had problems when the test was discovered. A symbol could not pass it.
We have cooperated with many third-party manufacturers, application software, and agreements are changed according to the requirements, which is very annoying. Some common situations, the field starting position of the agreement changes, the agreement is to be expanded, plus some content, more annoying some cases, the same application system, the agreement of several third-party manufacturers is completely different, So do a few sets of protocol interpreting procedures, I didn't expect this situation, and later changed the agreement, it was changed, while curse. At first, if it is expected to make this situation, the protocol is made into a plugin, you want to use that kind of that. However, this is also because of helplessness. At present, our products still have no strength to ask others to receive our things.
No one can see the ultimate look of the product in the initial development, develop a detailed plan, so the problems we encounter are almost inevitable, and we only want to reduce the probability of problems.
