[Learning] Development Process Design for small teams

This is written by brother rain (bluetent) and I am very touched by it. I am eager to find a platform for my ongoing or future work, realize your own greater value. Of course, we can find that the effective and reasonable integration of a company's internal resources often results in qualitative changes.

Click the picture in the upper left corner to see the flowchart. The following is an annotation of the line represented by each letter:
A. Communication between the project manager and the company's decision-making layer to determine whether there are sufficient manpower and feasibility to implement the requirement and the dependency with existing products.
B. The communication between the company's decision-making layer and the market/Planning Department will be quite adequate and will be repeated and long-term. It is committed to refining and decomposing the needs from the user's perspective.
C. The marketing department should communicate with the project manager on detailed issues to determine whether the requirement is feasible.
D, E, J. This is the architectural design process of the entire product. It is divided into two parts: UI architecture design and program architecture design. First, the architect must reach an ideological agreement with the project manager and then design the project. This design must facilitate division of labor, maintenance, and expansion, and be able to withstand a certain intensity of prototype development pressure. The UI architect separates the products based on the interface logic and knows the content to be placed on each interface. After a democratic discussion with all developers, the program architect develops a bottom-to-top program level (such as class and library ), function modules (such as homepage, content list, background management, and help system) are also divided ). The UI architect and the program architect need to reach an agreement on functional division, file naming rules, and so on, and constantly improve their thinking during development.
F. Artists use photoshop and other tools to design the interface and complete image cutting.
G. web designers are responsible for writing static templates. If there is a shortage of people, this location can be selected from the program developers.
K. coordinate between the artist and the web designer. The design thinking of some artists cannot be perfectly reflected on the webpage. Therefore, it is necessary to constantly break in and correct the ideas to achieve the satisfactory results of both parties. However, you do not need to make too many changes to the work completed by the artist. Therefore, one-way arrows are used here.
H. Organize the underlying logic (such as the design of classes, methods, and libraries) and related documents. If you have the energy, you can perform small-scale tests to ensure smooth development in the future.
I. After the underlying interfaces and related documents are completed, modular splicing will become easier. This process will complete the construction of basic modules to external functions.
L. This is the place where developers need to pay the most communication costs. Many underlying modules need to be changed during splicing, such as adding or removing parameters, modifying the names of classes, attributes, and methods, and moving classes, attributes, and methods. At the same time, the external implementation needs to be adjusted with the changes and optimization of the underlying module.
M. After the product is formed, it will be delivered to the testing department for testing. The test department returns a Report to the project manager and program developers. In a small-scale development team, a project manager can act as a Quality Assurance Team, provided that he has a certain degree of understanding about the project development process. Otherwise, A dedicated quality assurance personnel should be assigned to handle the bug list.
N. Reports returned by the test department can be sent to all program developers. Unfortunately, the testers only deal with the interface and focus only on the results rather than the implementation principles. Therefore, the bug list is generally handed over to the developer responsible for the interface logic for sorting, and then distributed to each member for correction. In small-scale development teams, the interface logic and the underlying logic may be implemented by the same group of people, so they need a Bugzilla to work together to handle these bugs. We also recommend that you use the same Bugzilla system to submit a bug report.

Summary: I. detailed division of labor aims to reduce communication costs. II. The actual situation will complicate the development work, so the process model should be able to adapt to the prototype development work. 3. Documents and standardized specifications are extremely important. They can make the development process factory and improve code quality and maintainability.