Time Scale: hour (1 ~ 2 hours), Day (0.5 ~ 3 days), Week (1 ~ 2 weeks), month (1 ~ March), Year.
The preceding time scale is used to measure the task. For example, it is meaningless to say that a task requires 10 hours. It must be converted into days, for example, two days.
Similarly, it may take 20 days to complete this user story.
The proper use of the scale will be very helpful for project management, and the pace of development will be well organized.
Task Granularity:
So far, in my practical application, the most basic unit of work for developers is 1 hour, which is also the smallest time scale above.
This is not necessarily the task assigned by the project. In most cases, it should be the decomposition task of the developer. the benefit of this granularity is that every hour you have a chance to breathe. in addition, there is also a definition of the mark of completion for the task. In other words, it is also an important factor that makes you breathe.
Project Scheduling task: 1 ~ 2 days is recommended, not more than 1 week.
User story: A week is recommended.
In addition, the relationship between the above concepts is: one user story can be divided into multiple project tasks, one project task can be divided by developers into multiple development tasks.