[This Week] Time Management in software development-where did my time go?

 

 

"Sorry, the project will be delayed for one week"

"Our project is delayed, but I cannot find the reason"

"We have completed 80% of things, and the project is going on as planned, but the system still cannot run"

Have you ever encountered these situations? Sometimes our project needs to be delayed, sometimes the project is delayed but cannot find the cause, sometimes the project is performed as planned, but we cannot get a molding thing when the customer asks about the progress. All the reasons can be attributed to the shortage of time resources.

How can we effectively use the time? Is it even effective to make full use of plans? This is our topic this week: Time Management in software development.

Let's analyze the above question: Why is the project delayed? Why cannot I find the cause of delay? This shows that the project execution plan is not refined enough. The details here are not extreme, but refined to the following level: with it, you can have enough clues to monitor the project progress and make real-time adjustments to the plan. This is our first point:The most basic Time Management in the software development process is to arrange a task schedule that helps you take control of the overall situation.

The next question is that our project is not delayed. When our customers or testers ask, we cannot find a system that can run temporarily. We can't help but say there is no delay. It seems that only we believe in ourselves. Of course, the development process cannot influence the outside world. However, why cannot a system be previewed first? This is the second point: Time Management in software development is very important ---Development task priority: the priority processing function is to help you maximize the benefits with the minimum investment.

How can we prioritize tasks?My article always provides an executable solution, not just asking questions. My answer is:Cearvr

CearvrIt is the principle summarized in military strikes, and some are written as: CarverI made an adjustment according to the thought sequence. CaervrIt is a practical principle that has passed the flesh-and-blood tests. When we practice it in the software development process, we will feel the greatness of this principle.

 

C: CriticalityImportance;The DLL used for sending and receiving an email may affect whether the entire process can run smoothly. Therefore, it is important. By contrast, a DLL that processes simplified Chinese characters on a page can be postponed.

E: EffectImpact;The development itself has deadline, and the page beautification work on the front-end and back-end management pages is not done. However, there are currently developers in the back-end management pages, and the impact of beautification is not great. The front-end page is the facade of the system, which has a huge impact, so it should be given priority.

A: AccessibiltyAccessibility;Can a task be solved directly, or is there something that must be done before it is done? If the service you want to write requires more than a dozen DLL references, and these DLL files are not completed yet, we think this service has no access.

R:ReturnReturn;The military pays great attention to the return of a military action, because each military action has a high cost. Without an appropriate return, this military operation fails. In one sentence, how much will you spend and how much will you return? It increases the coverage rate of unit tests without returning the development progress, or the return rate is very low. for users, you can tell them that your unit test coverage rate has reached 89%, he is not interested. He wants to ask you: can the project be delivered on schedule?

V:VulnerabilityEasy to complete; Is Your Goal easy to achieve? How long does this task take?

R:RecognizabilityUniquenessIt is meaningless to describe the plan "Monday system needs to complete 80%" and "Tuesday entire process needs to run" because it lacks the most basic Operability: on the one hand, the task content is not specific, on the other hand, it can be measured but cannot be measured. My colleagues are even more depressed: What should I do?

 

Conclusion: It is very important to have a time schedule for time management during development, and it requires a refinement that you can accept. Task Scheduling has a priority on the schedule. If you need a priority arrangement suggestion, I recommend:Cearvr;

There are a lot of books on time management and a lot of software. It is most important to find a suitable book and benefit from it in practice!

                                                                                                                                                                            Strong2002