-
Notifications
You must be signed in to change notification settings - Fork 11
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
Time label #41
Comments
@jackcarlisle great question! The time label e.g: This process is designed to help us all learn how to estimate our work and get better at communicating with team members and client. ⌛️ ❓ |
@nelsonic ok perfect thank you! |
at present our time estimate/actual labels are: #10 (comment) At present our two most active projects have the following Time-related Labels: @iteles can/should we have a |
I've observed that when we have too many of the 'short periods of time' labels, people have a tendency to underestimate. The "Oh, this will only take 10 minutes, but actually it ends up taking an hour" syndrome is something that happens a lot at the beginning of projects when a team is setting up or still learning to work together. Having said that, a task will extend to take up the amount of time you allocate to it, so a pomodoro seems like a good idea. |
@nelsonic @iteles When assigning a time label to an issue, does the time specified relate to how long it will take to work on, or how long it will be until it is completed?
Usually this would mean the same thing but I'm just wondering about when you're working on something in your own time e.g. at the weekend. On the weekend if I'm working on something I would take bigger breaks between stints. Does this factor in to the time that it is taking or should the time be purely how long you're spending in front of the keyboard?
Or should you not assign a time label because it's essentially bonus time?
The text was updated successfully, but these errors were encountered: