Effort and partial done function
For Scrum, and product development in general, estimating the effort required is useful in determining how much work and time is required to get to “Done”. As a general rule, there is often some difficulty in the accuracy of identifying how much time is required for a specific task or project. Scrum then uses effort to describe the complexity of the project. Scrum calls this “Story Points.” In Leantime, these are “T-shirt Sizes.” T-shirt size is defined by the team as estimations within a task. The team averages that a certain task is a “small” task and this second task is an “XL” task and so forth.
Partially done function:
This is a new feature since version 2.35. This means that a task can also be reported as partially finished. This is very important in productions, for example. If you have to make 1000 tables and it takes 10 days to produce. This allows production to increase by 10% every day. This means that the status is always more accurate and up-to-date!
The status of the milestones and projects is always calculated in connection with the effort. For example two tasks. A task with L (large) and a task with S (small) effort. If task S is finished, this means a lower weighting for the milestone status. This means the milestone is only 20% complete. Together with the partially done function, this becomes complex. If the S is only 50% complete, the milestone is only 10% complete.