Alchemy (2): why use issue management software

In project development , There are countless task decompositions , Problem management , Process tracking . Because directly speaking or directly in IM It's easy to shout in the , So in a not yet accustomed to use issue In the team that manages the software , Speak directly or directly in IM in AT, At some point it became the main task notification channel .

Like why we can't use IM Pass code to others , Let others cover their own projects . In fact, we should abandon the use of task decomposition and task tracking IM This way, “ facilitate ” The way of notification . Think about it , If you write a task scheduling system in your program , You will strictly design the manager of the task scheduling system 、 queue 、 Sort 、 priority 、 Execution time, etc . But when it comes to project development “ people ” To do , But you give up this kind of programming thinking . Instead, rely on that unstructured 、 Cannot be classified 、 Cannot distribute 、 Do not discuss with the subject 、 Not marked IM To do it , Isn't it stupid ？

How to be in a team In the effective use of issue Management software ？ A sufficient condition is that the project manager should take the initiative to rush ahead . No matter whether the members feel the habit , If the project manager strengthens the use of issue Management to create 、 distribution 、 Discuss 、 track 、 Eliminate task decomposition in project development 、 Problem management 、 Process tracking , that issue Management software is used effectively . It can be assumed that each member can only care about their own part of the task 、 problem , Instead of focusing on other parts . So project managers need to be aware of issue Keep track 、 to review a case , Grasp the overall progress and quality , Identify risks and problems in a timely manner , And give the necessary focus .

Choose what kind of issue Management software ？ There is a view that it is better to choose any one . In fact, this is just a subjective view , Some people have never used it successfully issue management , I think everything is the same , No difference . If so , Why does the source code management software need to start from cvs、svn、 To git Has been evolving ？ If so , Why? issue Management software people still need to develop better ones all the time ？ Good software is not used to keep up with fashion , But people don't have to deal with machines , Our human energy is the most precious , Should not be unknowingly become “ Inefficiency ”, hold 996 As a natural necessity .

Basically , If you feel git It is necessary and natural . I should feel issue Management software should be necessary and natural . You don't feel like using cvs, Should use the git. Then you should also feel that you should use some modern issue Management software , Instead of feeling indifferent , Just use an old one .

@ The treasure jade The following three obvious issue The benefits of Management ：

1. issue There is a life cycle
2. issue Is traceable
3. issue There are priorities

Why use tools , Because tools have put important things “ Programming ” Went in. .

--end--