Forum Posts

akter rojoni
Aug 02, 2022
In Welcome to the Forum
Every time you do a project, you may encounter online problems after going online, especially some abnormal logic that is not fully considered in the design, which will be exposed when users actually use it. It is not terrible to encounter this situation after finishing email list a project, because no one is perfect, and product managers are not gods. It is normal to miss some abnormal flows at the beginning of the design, but if every project misses some, or the same abnormality The problem appears many times, and this is the problem of the product manager. We can think that in the case that the business expansion is not so fast, the abnormal flow of the design at the software level is very limited. As long as one encounters it and solves it, it will always be eliminated. Product managers may spend part of their daily working hours dealing with the pits left by themselves, but when filling the pits, can we not only fill the pits, can we think about how to miss these abnormal flows, and Summed up one by one, this may greatly improve the integrity of product design. Project Management Before project management, you should first judge the type of the project. Different project promotion and management methods are very different. According to the size of the project and the degree of task parallelism, I divide it into the following three categories: 1. Large project management with a long cycle For projects with a long internal development cycle (more than 2 weeks) in a single department, I summarize the key points of project management as follows: (1) Communicate the development plan in advance Generally, larger projects have more complex functions. Therefore, the overall scheme design needs to communicate with developers in advance to clarify some key limiting factors and influence points, so as to avoid the scheme being infeasible during the requirement review, or the adjustment is too large, and it is difficult to reach an agreement at the review meeting. (2) Pay attention to the sequence of functions Pay attention to the interdependence of different functions in the project and the dependencies on external systems in advance, determine the scheduling rhythm of the project according to the order of functional dependencies, improve the degree of scheduling connection, and avoid a function that cannot be debugged with other functions long after the development is completed. , wasting development resources. (3) Strong impetus to the project Follow up the results of key points every day and discover risks as early as possible (in the form of daily reports, weekly reports, morning meetings, etc.).
Summarize the exception flow encountered content media
0
0
1
 

akter rojoni

More actions