Reflection on the problem of project promotion

Background introduction

The project of the quality platform was revised with the separation of front and back ends, because the data analysis system that had been built last year was a project of separation of front and back ends from scratch. This transformation was originally planned to be carried out using the original process and model, but after nearly two months Go slowly and start reflecting on the problem.

1. Untimely delivery and slow feedback

The interactive and visual content in the design stage was not enough to support the front-end design, but it took two months to discover this problem. There are two main reasons:

  1. Because UE still adopts the detailed design of one page by one page, it lacks the process of going from global to local and detailed, and jumps to the development of detailed pages in one step.
  2. And there is no staged delivery, or the staged time period is too long. If a page comes out first, there will be no risk of a lot of work rework if both parties agree to continue.

In conclusion, fast delivery of fast feedback ensures agility for the entire project and team

 

2. There is little communication, team members complete their own tasks individually, and lack of attention to the front and back links

Everyone performs their own duties and works diligently, but they do not pay attention to their upstream and downstream work. When they encounter new problems and new situations, they cannot solve them in time. Think of a sentence, if 1+1 is to be greater than 2, first of all 1+1 must be equal to 1

 

3. Do things in different levels. When and when you do things, you must be cyclically progressive and optimized layer by layer, not a sequential waterfall.

The first point of fast delivery is similar to here, but here's another question

Because it is a renovation project, I have a common problem in development. I want to fill in the previous pits, and I am still in the line-by-line coding stage. I want to develop every page in one step, and I want to correct every interaction detail. Carefully, I want the documentation of UI and UE to detail each mouse operation

When the leaders mentioned that they had to experience the internal beta version first, they remembered the level of doing things. The version is also iterative and progressive. The main process must be guaranteed first, and then the details can be optimized step by step. Dive into the details and make another design-phase mistake

Therefore, keep the alarm bells ringing, and really remember all the time: no matter when or what you do, you must progress in a hierarchical and circular manner .

 

4. Be sensitive to issues

In fact, before the project problem broke out, I already felt unhappy that the things delivered in the upstream link were not always what I wanted, and there was always a gap between what I imagined. However, he didn't reflect on what he wanted. What's causing this? I didn't even think to solve this problem. Now that I think about it, this is the most terrible thing. This may be the soft skill that many people say that programmers lack the most.

If you want to improve, you must pay attention to when you are unhappy at work, and you must be sensitive to your emotions about work. This time is mostly when you encounter problems. At this time, it is necessary to jump out of the specific task in hand, organize the process of things, and think about how to do this thing? Sometimes thinking about this problem can really do more with less.

 

5. Minimize the coupling of each link of the project, and do not rely too much on the connection between the front and rear links to ensure the overall progress

This should not be said too much. It is the same as the design method of software. Problems in any link should not make the whole task stagnant. Although the work sequence of the front and back is inevitable, it is necessary to minimize the unnecessary coupling of upstream and downstream. On the one hand, it can be Improve efficiency and, on the other hand, enhance the project's ability to resist risks

 

I just started to write a summary. I guess no one can understand it except myself. Haha, it’s too late to polish it, so let’s do it for the time being.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324911570&siteId=291194637