Focus on the front-end development process

Process, popular speaking, is a lot of people, in doing a series of things, how to coordinate with each other, arrange the sequence of things, what the prior agreement, need to achieve what the expected goals.

In the ued, the front-end students need to deal with more needs, earlier, the front end of the development process is still relatively vague, ued outside of the students are not clear how the work in particular is how to carry out, so there will be a need to jump the situation occurred, disrupted everyone's plan, so this year Q3, In collaboration with the SCM team of students, the formation of a front-end assets release process.

This process focuses on the requirements of the assets release, and has established several relevant points of time, including audit requirements, submission code, daily test, pre-release testing, official release to online confirmation time.

Assets Process Brief

Requirements Audit

Before the demand, the demand side will generally find the PM or the corresponding product line front-end consulting, if feasible, will be in Thursday before the requirements mentioned on the platform, to the Thursday, the front-end will be combined with their own work, the platform needs to receive and into their own schedule, estimated completion time, Release time and related release briefs.

Coding development

After the Thursday needs assessment, the demand will begin to be processed as planned, and the demand for assets release will be dealt with as a priority, not involving assets in the back-end time, usually from Thursday to the next week of Tuesday. SCM will open a new assets branch every Thursday for the front end to be developed for use next week.

Submit code, merge to daily test and pre-send test

If there are requirements related to background development, the front-end alumni will submit the code in Monday, a day of merging code that facilitates background development to test. Other students in the most party in Tuesday before work before the code submitted, in Tuesday, there will be many times to merge the code to the daily operation, after each operation, SCM alumni in the front of the group notice to everyone, convenient for everyone to test.

In the morning of Wednesday, the SCM alumni posted the code to the pre-launch environment, where they could bind the IP in host, swapping the address on the line for testing.

Official release

In the morning of Thursday, when the classmate of SCM confirmed, the code of No problem was released online.

the role of the process

As the team grows, the number of requests that are processed is growing, taking into account the efficiency of development, the quality of the product, and the coordination of teamwork, which can solve many of the related problems:

Urge the demand side to do the relevant planning

Sometimes, the details of some of the requirements are not yet fully identified, but the demand side always wants to be able to bring out all the details he thinks of, and then pick one of them as his plan, so there will be a lot of changes in demand, but the cost is a little high, and everything should be done after the plan, not the opposite. Now the demand side will take time to consider their needs before the demand, will be as much as possible to think clearly, do the necessary communication work, weigh the pros and cons, and then give a more formed scheme.

Ensure the order of demand arrangement

In a large team, students from different departments work together, because communication and some special circumstances, efficiency will be more or less affected, good planning can help improve the efficiency of development.

Through the weekly needs audit, scheduled for the next week's schedule, due to the needs of priority and sequencing have been scheduled, the work will be more organized, the need to queue the phenomenon has also been significantly reduced. Of course, we also have an emergency process, but it is limited to dealing with online bugs and a number of recognized emergency needs, has its own scope of application.

Unified testing to avoid risk

In your previous routine, you might experience a situation like this: A, b Two students need to deal with two daily needs, their need to change to the code will have overlapping parts, if they do not know this situation, then in their own local test, everything is OK, however, when posted to the line up, found that the bug or one side of the changes did not sync to the line, check the reason found that the submitted code to cover each other.

Now to deal with more and more requirements, in order to avoid this situation, the new process after the implementation, we will be unified to do multiple tests, so it is easier to find bugs, can greatly reduce the risk of collaborative development.

The process itself is a double-edged sword, both pros and cons. On the one hand, it makes our needs orderly, so that the front-end can deal with a demand, will not be frequently interrupted by the needs of other queue. And because the release has a time point set, the test work will be more rigorous, which helps improve the quality of the code. So for us, the benefits of the process are obvious; but on the other hand, it increases the cost of doing things, involving the demand of assets release, just like catching a train, missed can only wait for the next class, so also to the demand side brought a lot of inconvenience, need to improve, But this can be slowly weakened through long-term cooperation, the two sides reached a tacit understanding, the situation will be much better, now this situation has been relatively few.

While it can be a lot of inconvenience at the beginning of the process, in the long run, the process helps to make a team work in a uniform way and attitude, breaking things up and dealing with them methodically. Because of the process, each person's sense of responsibility will be enhanced, the risk considerations will be more, all this will make the product quality promotion. And all of us who are involved in this process are constantly driving the process improvement work, and there's a lot to think about:

• How to extend our process to the whole company, so that everyone can understand our process, so in the future need to cooperate, the demand side need to pay attention to what, the relevant points of time and the estimated time of the week, they will know.
• Assets release is not flexible enough, if and application-related assets independent division out with the application to publish, so that the rest of the need to release a lot less things. or by product line to design the release process, according to the actual situation to release.
• How to simplify some of the details of the process, while maintaining efficiency, while reducing the cost of the actual operation.
• The second of the week is a special time point, in order to catch the last time to submit code, the previous development will be a little nervous, this situation also need to improve, such as the future can be two times a week release.

The process is not inherently perfect, but from what it brings to us now, following and using it will be of great help to our development. Our attitude towards it determines how it will respond to us, if it is not appropriate, send out its own voice, try to improve it, do not just wait passively.

———————————-

Some nouns explain:

Daily Environment: a day-to-day test environment for ued
Pre-issued Environment: extranet IP, need to bind access, for internal use test
ASSETS: Directories stored in scripts and styles
SCM: Software Management configuration
PM: Project Manager