Title: No head, no tail - Project Development Notes: Last Notes
Keywords: technical mentality summary
March 29th: The panic of the in -ode pneumonia is propagated with the most advanced pathway. In addition to anyone who doesn't care about the poor Iraqi people
Maybe when I started the name, I didn't have the name, I didn't adhere to the finals in the project, but left this project before the project was completed. The project is dedicated to the technical manager by the colleagues responsible for the design and development of the client. How many months of development brings me a lot of ideas, a lot of gains. The process of writing a project development notes also makes me know a lot of good friends. This is the last project development note, the main project team in choosing some changes in the project development language mentality. Upset project notes "No head without tail - Project Development Notes: How to choose a project development language ?!" There are some descriptions, but the idea has some changes in two months, and the project team is recorded here. Three changes in the technical mentality used.
Three stages of technical mentality
Due to many changes in the mentality of the members of the application new technology project team, we also pay great expenses for these changes. The first is to directly lead to changes in the mentality of project team members, and then the impact on the mentality of the technology must be put into investment in the project. Finally, the progress of our project is affected. Perhaps some questions go into a mentality, or if you guilty in your mentality, it is not completely correct. But I want to summarize the changes in these mentality, making everyone can adjust their mentality when they meet the problems in the project, thus making correct judgments and processing on the project.
The project team has three stages of the adoption of new technology development projects, which can be said that the emergence of these three phases is very meaningful. Here is a description of these three phases. And explain what positive negative impacts from the changes in the mentality, respectively, and the impact on the cost of the project.
Fanatic
Some Demo has been made between the initial period of the project. And from the data and DEMO, the way to adopt (you can see the previous project development notes). It can be said that members of the project team are excited for this technology framework. Everyone concentrated on a lot of enthusiasm in conducting discussions on the project model, and made a lot of experiments, a large number of DEMOs. It has made a certain technical foundation for the development after the project.
u benefit
1. Participated project team members learned from the project technology framework for future development; and enable the members of each project team to enter roles.
2. The project team has specified that most members only have the basis such as VB, and the technology based on DOTNET development is unfamiliar. Through this fan, the project team members quickly familiar with this new development work and development.
u
1. Extensive production of Demo makes a research on the framework of the technology, there is a non-despiced atmosphere. Specifically, it is a lot of time to discuss Facade every day, and the discussion every day should eventually be divided into several layers. The stuff to consider in the frame design such as efficiency, security, and exceptions is placed behind. That is, the enthusiasm of the technical framework has made us a chaos for the distribution of working hours and work.
2. The demand and design are placed in a secondary location. Since I don't know much about business, I didn't go to members of the project team to make a detailed admission ticket, and become design. But only from my perspective, the needs of the most crude granularity can be said to have no effect on the progress of the subsequent project. This also describes in the previous document.
3. Only from DEMO, the issue of the project is derived, and there is no developmental feasibility analysis. Leading the project has passed a lot of detours in the early days.
The benefits and disadvantages speaking above, my experience is that there is a good factor in the project development, and it is necessary to maintain a clear mind. Always use the project itself as the starting point and the destination. Not all people in the project are frenzy and research is a good thing, but should be considered to consider whether there is any benefit of the development of the project?
2. Disappointment and depressed projects, due to changes in development modifications (mainly referring to the development of Delphi), it is not very sufficient. In particular, the development mode changes is too short. Issue and preparation for interfaces for interfaces through Web Service through Web Service. So although our program has a lot of advantages, the corresponding development process is very hard. Due to the low development efficiency, the time of the project is very tight, coupled with members of the individual project teams continue to promote the development of the project from time to time, and should not use this new technology to develop. Leading from the initial enthusiasm from the technical framework to the technology very disappointed and frustrated to the project, many project team members think we have a wrong choice and push the responsibility of the project's extension. This reason.
I feel very uncomfortable on this thing. I didn't make my own analysis based on the mentality that the project team members appeared in different periods, and the way of identifying the method should be adjusted. In the previous stage, I am a fanatic molecule and there is no awareness. At this stage, I have become a disappointment and frustors, and I didn't take careful analysis because the error is due to the choice of development methods or due to development methods The depth of research is not enough. This comprehensive disappointment and depression emotions have huge impact on the project. Our development efficiency is low, and we no longer be proud of the project itself. Until the next mentality phase. Fortunately, although there is a disappointment in this period, we still insist on the rules of the original definition. It's still insisting on the defined technical framework.
3. Plain and numbness (experience best choice)
The project team member is no longer concerned about what kind of technology used for projects. That is to say, it is possible to view technical problems with a mentality that is more normal or numb. The following conclusions can be obtained by careful investment project itself.
1. This project must use the web service to complete this project.
2. When the project selection, developing Web Service is more mature technology may only have DOT NET and JAVA development tools. From the original technical foundation of the development team equipped, you must choose DOT NET. (Delphi7 can develop Web Service later, but we don't have time to change our development method.)
3. By investing in other companies' development products, this way is also the choice of many other companies. It can conclude that this development method should be very advanced and popular, and have a strong vitality.
From the above list, conclusions can be concluded that VS.NET's server-side development Delphi client development is "best choice" to complete the project in our special environment. When I got this conclusion, I didn't have a breather, but in the process of lament, I have gone so much detail due to the changes in my mind. Due to the frustrations encountered during the process, there is a significant impact on the development of the mentality of the group's membership, which affects the efficiency of the project, and has a lot of negative impact on the progress, cost and quality of the entire project. How to face these mentality changes, how to adjust yourself, and the mentality of the adjustment of the entire project team related members, this is the project manager should carefully consider. Many times when you are in the bureau, you can see all things, you can use the right way when you finally conclude, but it is too late to lose.
It's easy to say something, in fact, I think the changes in the technical mentality and the changes in the communication of boy and girls in life are very similar. After the initial love (fanatic) to live together, I found that the other side did not expose the shortcomings in the process of love, so I felt depressed (disappointed and frustrated), and found her (or him) after the baptism of life. Your "Best Choice" :) In fact, there are similar processes in many things in the world. Is the friend still think about it again, are you also in love? There are a lot of experience in mental change. Is it possible to control these mentality changes make your life (project life or love life) more successful? Haha, don't teach too much. Write in the last words
Thank you for your attention to the no head - the attention of the project development notes, friends gave me a lot of good suggestions and brought a lot of help to the project process. Of course, I also hope that my mistakes I have been able to make mistakes when I meet, and I hope to continue to communicate with my friends. Mailto: Viktoryu@hotmail.com. Ok, "no head is not tail" is over, if the next project can say the Dongdong, I will write the project to develop notes and friends, have any friends to give me the next project development note naming suggestion Yeah?
