This is how programmers make (8)-1 + 1

I had to work overtime until today. Recently, the entire project team was busy because of the sound of no aquatic products. The original arrangement was for group A and group B to complete two projects respectively, but the trouble was finally caused by unreasonable assignment of work tasks.

The task of group A is to build A customer project, which is planned to be completed in March, with A workload of 60% RMB.
The task of group B is to develop A platform to support A series of future customer projects of group A. It is planned to be completed in May or later, the developed platform will be used and maintained by group A in the future. The workload is 90%. We can understand that the project in group A is A subset of the platform in group B.

However, some time before the launch, the project manager of group B was not strong enough. As A result, the progress of group A's project went far beyond the previous stage. All the ideas and designs were completed, and group B had no improvement. Group B's inertia ideology began to blame and has been the design and creativity of the followA group. At the beginning of Group A, Group A was also happy to provide support and help for Group B, hoping that the development platform software they will use in the future could be improved. It is hoped that group B will improve other functions based on its existing functions and complete A stable platform software for future use of group. In this way, the two project teams will work together, and the two teams will be more harmonious. However, it was not A long time before the conflict broke out on this Monday. The fuse was that group B decided to use another programming language to implement it again along the path opened by group A and complete its own tasks. Group A's desire for joint development was shattered, and the time for group B's support and training was lost. In addition, group A complained that group B was completely wasting the company's resources.

The company now faces four options:
1. Let Group A and Group B continue to complete the developed tasks in the plan, and there is no need to manage the tasks. The Chu River and the Han Dynasty clearly painted the two groups.
Potential risks may be:

(1). Overlapping programmer development brings redundant work to the company.
(2) In the future, group A programmers may prefer to modify their original projects to meet new requirements, and the platforms developed by group B may be out of demand, there may be no users, and the developed platform group A will not accept it.

2. Group A stops the existing project, develops the platform together with group B, completes the project in group A during the platform development process, and then completes the tasks in Group B together.
I support this, but the potential risks are:

(1) strong opposition from Group B's project managers. Group B's site B is the master.
(2) who will manage group A and group B in A unified manner? OrB leader. Will A's enthusiasm be frustrated?
(3) Group A's energy will be spent by the platform project. If group B can work hard, it is the final result to catch up with the win-win situation. If group A is dragged back by group B, the project will be postponed, the customer cannot be told.

3. After group A completes the development of the existing project, continue to develop the platform. You will also need to use it after group. Staff in Group B are transferred to start other projects.
Potential risks:

(1) If the tasks in two groups are attached to one group, can the team members in group A take on the important responsibilities?
(2) How can we restore group B's morale?

4. Let group B's staff go back to the common development path. The company does not need two platforms.
This problem should be very good as a project management question. I mentioned it here because I think we will encounter many irreconcilable conflicts in daily project development, it is impossible for all colleagues to develop based on your ideas. We should learn how to face it. How are you smart? What do you do if you are A member of Group A or Group B? What would you do if you were a project manager?

Ah ~ This is probably the cause and effect of the incident. At first, assigning tasks to Group A and Group B is problematic. It is really difficult to find A correct answer from A wrong start point.

My thoughts and choices are definitely not the best, but I still want to share them with you. 24 hours ago, my views have always supported 4th choices, since A + B has passed A honeymoon period ~ Otherwise, let them complete their honeymoon. However, project A and Project B managers cannot communicate with each other, just as the two cows cannot pull in one direction, and there is no result in repeated negotiations. After the debate on Monday, my point of view has changed. I am wrong. I support the improved version of the 3rd options. Group A develops the existing project and continues what group A thinks is correct, the development platform should be used by itself in group A anyway. It is better to let them do it. Group B personnel are not moved away for the moment, but still their own development platform projects. Just like in the revolutionary period, Lao Mao said that he would go north to resist Japanese aggression, while Lao Zhang said that he would save the nation in the South and that the two revolutionary troops would not be able to go one by one. Then, let alone fight for the winner. As A result, no matter what the final platform of group A is, Project A and Project B cannot be completed on time, and no excuse or reason can be found, if all are completed, the basic requirement is met. If you are lucky, group A may have unexpectedly gained two software platforms. We can also choose the best one. Since the two groups like to compete technically, we don't want to persuade them ~ Then let them drag out as musters and horses. By the way, it will stimulate the enthusiasm of group B. If group B is defeated and the development team is trained, you can find a reason to rectify the problem, he is happy. If the final platform of group A is not selected, they will certainly lose their minds. From the results, the company level is acceptable. Let's look at the time. After group A completes the planned project in June, the time spent on continuing to develop the platform is the additional development cost that the company needs to pay. However, since both parties call them strong, I feel that the actual development time of group A and group B is one or half A month less than expected. That is to say, in terms of time, the company's resources will not be wasted. It may be shorter than before.

During our daily development process, I believe this will happen frequently. I think it is necessary for everyone to think about the problem from the company level and become a technician, do not care too much about your own gains and losses, credit, project leader, and project manager. First, what can we bring to the company? What can I bring to our team and what I can learn. In fact, this real thing I encountered today, from the project plan, to the start, to monitoring, there are people making mistakes in every step. How to unite the team, save resources, and make every colleague gain something in the project is to save the programmer's youth and life. How to achieve 1 + 1> 2 is our daily work, the division of tasks should be understood by people.