-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Estimated Hour #93
Comments
how do we know the issues for next week ? by start date ? or by due date ? or by both ?
|
I think by start date. "Due data" only fill when the issue has done. Yes 2 reports.
One example: We have 3 issues done the last month. One issue estimated in 100h, other issue estimated 25 hours and other estimated in 25hours. (150hours) The 150 hours are assigned to a one user. If i want see plan for next month i have to see that one user work 20 days * 8 hours, in total 160hours. I can see that the user need 10 hours more of workload to complete the month. If i want see plan for last month: i see, for example, that the user has needed 160 hours to end 150 estimated hours. I have a problem to estimate the work. Or i see, for example, that the user has needed 140 hours to end 150 estimated hours. The user is more efficient and for this the bussiness won 10 hours more. And the user had 10 free hours that could have been exploited. Or i see for example that the user has needed 100 hours to end 150 estimated hours. As the first example i have a problem to estimate the work althout in this case the bussines not lost money. |
Some times its necessary known the load for next week to do a plan. The issues of next week only have estimated hours.
Can be interesting generate a report with time estimated vs time dedicated.
The text was updated successfully, but these errors were encountered: