Record the "problems" encountered in an outsourcing process and the "countermeasures"

This article from: http://www.cnblogs.com/JavCof/archive/2011/03/14/1983072.html

 

 

After receiving an order from an agent, the company decided to outsource the project, so I recommended myself as the owner of the outsourcing project, next we will record the problems encountered in this process.

1. Who is there for outsourcing? Is there no stable target for outsourcing Supply and Demand?

2. How to control the quality of outsourcing projects and supervise the process? How can we control the construction period and maintain the project in the future?

3. How to analyze the demand? At what level?

4. On the user interface, who will design the database and who will complete the system framework?

 

In combination with the above problems, I woke up myself, and outsourcing projects are definitely no more easy than doing it alone. In more cases, you can examine the problem from the perspective of a project manager.

Let me list my solutions. -,-

1. I chose a friend who is familiar with outsourcing, because everyone is doing this. NET development, usually nothing, also talk about technical matters, is a good candidate, at least much better than looking for strangers on Weike.

2. a. for outsourcing Quality Control, we have adopted the upper-layer framework (ORM layer and common Layer) of our own project, and outsourced personnel (business logic layer and webui layer) method. This seems to be contrary to the original intention of outsourcing, but it is really easy to know how to control the quality of outsourcing projects. There will be no N projects or N frameworks. (-_-|)

B. for the issue of process monitoring, the project uses SVN for remote collaborative development. Fortunately, everyone is familiar with this software, and the problem is not too big. However, the project process supervision and project evolution, it really plays an important role.

C. period control is the biggest headache (the original model method is used to make a system prototype in the shortest time, and the system is continuously improved through in-depth and evolutionary methods, this effectively saves the scheduled time cost)

D. Later maintenance. here we can use the development logs left by SVN. (P.s. SVN is really a good thing. Thanks to the special remote collaborative development, VSS is too stretched)

3. The requirement analysis should start from three aspects: User Interface UI, database design field, business logic function, and system function description.

4. A. the user interface is designed by the outsourcer. Based on the requirement analysis document, design the corresponding business form and submit it to us for review. After the application is approved, proceed to the next step. Here, the designers will examine the project from the user's perspective, and their understanding of the project will be further improved. I call him UDD (User Interface-driven development) for the time being. Here I think of it as the charm of TDD. The User Interface goes first. Through the feedback interface, it is obvious that the outsourcing party has a solution to the business (either over-designed or not in place) and communicates with friends through QQ, discuss and modify the business form. B. for database design, we have a deeper understanding of the business than the outsourcers. While the outsourcers are designing forms, we are also designing and modifying database fields, finally, a database prototype is completed, andCodeGenerate the data entity layer and submit it to SVN. (We designed a database to meet the requirements of standardized data fields ).

 

Project Progress: the project is now being delivered to the customer for acceptance and is expected to pass the acceptance as soon as possible.

After receiving an order from an agent, the company decided to outsource the project, so I recommended myself as the owner of the outsourcing project, next we will record the problems encountered in this process.

1. Who is there for outsourcing? Is there no stable target for outsourcing Supply and Demand?

2. How to control the quality of outsourcing projects and supervise the process? How can we control the construction period and maintain the project in the future?

3. How to analyze the demand? At what level?

4. On the user interface, who will design the database and who will complete the system framework?

 

In combination with the above problems, I woke up myself, and outsourcing projects are definitely no more easy than doing it alone. In more cases, you can examine the problem from the perspective of a project manager.

Let me list my solutions. -,-

1. I chose a friend who is familiar with outsourcing, because everyone is doing this. NET development, usually nothing, also talk about technical matters, is a good candidate, at least much better than looking for strangers on Weike.

2. a. for outsourcing Quality Control, we have adopted the upper-layer framework (ORM layer and common Layer) of our own project, and outsourced personnel (business logic layer and webui layer) method. This seems to be contrary to the original intention of outsourcing, but it is really easy to know how to control the quality of outsourcing projects. There will be no N projects or N frameworks. (-_-|)

B. for the issue of process monitoring, the project uses SVN for remote collaborative development. Fortunately, everyone is familiar with this software, and the problem is not too big. However, the project process supervision and project evolution, it really plays an important role.

C. period control is the biggest headache (the original model method is used to make a system prototype in the shortest time, and the system is continuously improved through in-depth and evolutionary methods, this effectively saves the scheduled time cost)

D. Later maintenance. here we can use the development logs left by SVN. (P.s. SVN is really a good thing. Thanks to the special remote collaborative development, VSS is too stretched)

3. The requirement analysis should start from three aspects: User Interface UI, database design field, business logic function, and system function description.

4. A. the user interface is designed by the outsourcer. Based on the requirement analysis document, design the corresponding business form and submit it to us for review. After the application is approved, proceed to the next step. Here, the designers will examine the project from the user's perspective, and their understanding of the project will be further improved. I call him UDD (User Interface-driven development) for the time being. Here I think of it as the charm of TDD. The User Interface goes first. Through the feedback interface, it is obvious that the outsourcing party has a solution to the business (either over-designed or not in place) and communicates with friends through QQ, discuss and modify the business form. B. for database design, we have a deeper understanding of the business than the outsourcers. While the outsourcers are designing forms, we are also designing and modifying database fields, finally, a database prototype is completed, and the data entity layer is generated through the Code Generator and submitted to SVN. (We designed a database to meet the requirements of standardized data fields ).

 

Project Progress: the project is now being delivered to the customer for acceptance and is expected to pass the acceptance as soon as possible.