[beauty of software engineering - column notes] "one question and one answer" issue 2 | 30 common software development problem-solving strategies

---

Column information

1. Columnist ： The treasure jade

2. Column publishing platform ： Geek time

---

primary coverage

One question and one answer

1. ask ： Feasibility analysis is in vain , The job responsibilities of small companies are not clear , Take care of each other's face for fear of offending others , Everyone is afraid of making mistakes , It feels like everyone is right , It will eventually lead to who is “ Boss ” Who makes the decision ！ I feel this problem is quite serious , It will affect the correctness of decision , We can only wait for the so-called market feedback . Also use similar project members “ Poker ” Can the scoring method be solved ？ What's the core problem ？

   answer ： This problem is no longer the problem of feasibility study ！ The core problem is that there is no reasonable mechanism and process similar to poker scoring .

   Why is playing cards a good mechanism ：

   • fair and reasonable , Everyone has the opportunity to express independently of others
   • Don't carry the pot , It doesn't matter if the estimation is wrong , Disagreement can also be discussed

   Can the feasibility study also form a similar mechanism ？ There are special meetings , Everyone prepare in advance , Discuss the results together at the meeting , Don't carry the pot , Form a final decision according to the discussion results . Review and compare the original analysis after the project , As the next reference .

2. ask ： Whether architects also belong to the category of managers ？ Because he needs to be responsible for the whole framework of the product , Then it involves the management of everyone's code , When necessary, it is necessary to lead team members to tackle key and difficult problems . So for architects , Is it more technical or management oriented ？

   answer ： I think there are similarities and differences between architects and management , To put it simply, my point of view ：

   Similarities ：

   • We all need to look at the overall situation ;
   • All need good communication skills , Let the team clearly understand their intentions ;
   • We need to make good use of processes and tools ;
   • Be good at “ Divide and rule ”, Break down complex problems into small specific problems .

   The difference ：

   • Project managers deal more with people , Be responsible for the project ;
   • Architecture design focuses more on Technology , Be responsible for the architecture .

   They complement each other , Architects have the ability of project management 、 The project manager has the ability to structure , All very good ！

3. ask ： The consistency of goals is the difficulty encountered , The company has no incentive system , As a result, the objectives of the project manager and team members are inconsistent , How to solve this problem is very difficult .

   answer ： Solve the problem of goal consistency , One way is to communicate one-on-one , You know what the team members think , Team members know your expectations ; Another way is not to rely on the existing system of the company , Create your own incentive system , Incentive system does not have to spend money or spend a lot of money , Sometimes formal praise is more valuable than money .

4. ask ： How small companies manage technology ？ My company , More developers 40、50 people , Less 10 More than one person , This stage , Is to use the system to manage , It is more suitable for people to manage ？

   answer ： I think no matter how big or small companies , We must use more reasonable systems and processes , Use more tools , Get rid of excessive dependence on people , Only when designing process specifications , We should fully combine the characteristics of the company 、 Project features .

   For example, the boss of a small company has great power , Some processes are effective for ordinary employees , The boss directly ignored , You have to take isolation measures , Ask him not to break the process . For example, large companies have many tools 、 The systems are self built , Small companies are not as cost-effective as buying them .

   There are relatively many meetings and documents in large companies , Small companies can be more streamlined , But it is also necessary ; Big companies use waterfall models to develop , A project can afford several years , Small companies should be more agile , It's better to see the output early . One day in the future , Small companies will also become large companies , If you haven't done a good job in system construction before , In the future, the team will grow , More projects , It may become your management bottleneck .

5. ask ： The success of the team , Is your success , I used to believe in this view , But its own example , Let me waver a little . Train the subordinates , The result is not a promotion , But my superiors are increasingly marginalizing me . In this case , How to adjust yourself ？
   answer ：　 The mood is completely understandable , But the suggestion is to look at the long term . Life is not just a subordinate , Not just a boss , It's not just a project . I've struggled with this problem before , I don't think so now . Because I can not only cultivate one subordinate, but also cultivate more subordinates , I can do one project well and more projects well , I don't need to rely on the appreciation of a boss to prove myself .

---

summary

Project management runs through the whole project , Demand is the source of the project .