Project management: Party A and Party B

I recently took over a project,

Party A: When a state-owned enterprise has money, land, and communication with customers, the most common saying is that money is not a problem, technology is terrible, project management is absent, and the interface department is the Information Department, there are more than 60 people (only for Visual Testing) in it. Most of the contact persons are just graduated from college or have been working for a year or two. They basically have no development or project management experience, every day, you will be followed by a dog, but the execution capability is super powerful. As long as the leader speaks a word, it must be implemented. (If you stay in the place for a lifetime, do you still want to have a good life for your leadership? In fact, they chase you every day because they have no implementation capability)

Party B: A large outsourcing company. The number of employees is W. The overall quality of personnel is poor, the professional ability is poor, the overall ability is worse, many people come, many people go, many people are mixing, there is no process, there is no management, live off is a black software workshop.

Let's talk about the project. It is said that this project has been in operation for 10 years. I have roughly read the code, no architecture, and only a simple design. The code is estimated to have been changed n times, hard coding is everywhere, and technology lags behind, not even the most basic test and development processes.

Unfortunately, I became a project manager for one of the sub-projects. After a week of observation and summarization, I came to the conclusion that the existing development and management modes are the best, and any change to management and technical improvements will not work, because the customer is too dependent on Party B, and does not have the ability to manage the most basic project, and Party B has achieved the ultimate in cost control, so that it has to apply for a network cable, in this environment, you have to share all the water and electricity generated by working overtime. In this environment, you cannot recruit people who can do things, project management tools, and test tools, source code management and version control are all nonsense for them. The project team members can mix up with each other and are not afraid of your speculation ), basically, when a monk hits a day. For such customers, anti-project management and anti-pattern are required for such projects. The most effective method is one-on-one. Every day, one or more customers can face the customer. How can customers change the project if they want, achieve "real" Agile development. To put it bluntly, how can we get it easily, how can we get it quickly, process, management, technology, and architecture!

Project management: Party A and Party B