Thoughts on front-end development and management of web projects

Thoughts on front-end development and management of web projects

 

Transferred from: Web Front-end development

 

Web Front-end refers to the combination of interaction, design, and production roles.

Project management refers to how to break down requirements into tasks, assign them to appropriate people, and complete tasks correctly.

You must be aware of the following:

1. Requirement Analysis

The purpose of requirement analysis is to review the feasibility and priority of a requirement. Sufficient project experience is required here.

Feasibility:

Whether the requirements are reasonable or not is a worthwhile requirement.

Whether the requirement is complete or not can be entered into the R & D planning requirement.

In fact, there is also a demand adequacy, which combines scattered small operation requirements into a large demand for easy development, so that the task list is clear and concise, and maintenance risks are reduced.

Once again, it needs to be developed in the background for communication, whether the next R & D line can be reviewed and followed up on time.

 

Priority. Priority is based on Importance and closeness. Draw a two-dimensional coordinate axis to clearly distinguish it.

1. important and urgent requirements certainly have the highest priority.

2. Important

3. The emergency is not important again (pass may be required, rarely seen)

4. not urgent and unimportant last (basically none)

Depending on the nature of the product, the product can be further divided based on the above, such as platform, value-added, and operation (bug fixing and small experience optimization ), daily Maintenance (periodic O & M requirements, slice design, fixed mode activity requirements, etc.) can be filled in four quadrants of two-dimensional coordinates.

2. Break down tasks

How to break down requirements into feasible tasks is generally a rolling task of interaction-design-making a line. Tasks include content and development cycle.

1. New Version R & D needs to be planned.

2. There are fixed activity demands and project planning is required.

3. Activity requirements: this type of project is a complete and relatively small project, but it requires interaction, design, and production.

4. There are a lot of operational requirements, which are complex and fragmented, not all of which involve the three roles.

3. Task Assignment

The purpose of task assignment is to assign the task to the right person at the right time on the basis of the first two tasks. The capability gap between people and people exists. Therefore, the important and difficult requirements are assigned to more competent and experienced people, which are sorted by importance and difficulty, there are also familiar tasks assigned to familiar people (someone has been following up on this demand ).

Task time distribution, which decreases sequentially according to the importance and scale of the task. The specific time needs to be determined by multiple parties. However, based on the previous Task completion status, you can evaluate the production capacity. The unit of the number of persons/days used can also obtain a rough time point.

4. Task Quality Review

This shows whether the task meets the requirements after the task is completed.

Basic Quality: Interaction integrity, design draft integrity, production integrity

Advanced Quality: these are difficult to estimate and need to be judged based on different fields. For example, the experience of interaction is strong, the visual presentation is in place, the production is easy to develop, and the design draft is restored, open speed improvement, etc. More is the quality evaluation of the technical team.

This is only the most common point in project management. There are many other crisis solutions, project process standardization, and assessment system regionalization, I hope you will have more exchanges with us with this experience.