How can the software development team avoid working overtime as much as possible?

In software development companies or departments, working overtime is usually a very common task. When software development friends get together or communicate with each other, they will ask: "Do you have to work overtime ?"

It can be seen that overtime is very common for it men/women, but it is inevitable. Then I will talk about how to avoid it to some extent based on my experiences:

-------------------------------------------------------------------

As a developer with an architect (development leader or something like that), you can do a lot: 1. clear thinking: actively participate in requirement analysis, refine functional points as much as possible, and eliminate situations where different requirements are understood. 2. priority: The development tasks undertaken must be completed according to the demand side (product manager or external customer) evaluation priority from high to low, to avoid chasing branch issues and putting the cart before the horse; in addition, it is very likely that the project progress will be postponed because the task is not completed according to the priority, and you will become the short board that leaks water buckets. 3. reasonable disposal of demand changes: the only thing that remains unchanged is demand changes. Changes to requirements should be arranged in the next iteration cycle as much as possible to avoid impact on the team's development progress caused by direct insertion into this iteration cycle, you know the KPI assessment. 4. Active delivery: the fulfillment degree of functions should be instantly known to the demand side, so as to avoid development risks such as inconsistency between requirements and development and missing functions, and eliminate some bugs. 5. iteration cycle arrangement: as short as possible (1-2 weeks is recommended), in order to quickly locate the development target. 6. Team Cooperation: The personality, run-in, morale, and other factors that affect the overall efficiency of the team should be actively concerned. 7. New technologies: the research and application of new technologies may affect the development efficiency (both reducing and Improving the efficiency may be) and should be evaluated objectively and fully. 8. Self-management: arrange work properly and spend 10 minutes planning a day's work every day. A good habit can create a successful male (or female). ^_^. 9. productivity: divide 8 hours (for example, 7 + 1, or 6 + 2). Here, 7/6 represents your work time (for company affairs ), 1/2 represents the time for you to open a webpage, open a gap, and relax. Only by strictly separating work and entertainment time can we truly concentrate on completing only one task in a period of time. Arrange your own time and do not allow the leaders to passively accept it.