Skip to content
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

Open
jackcarlisle opened this issue Oct 22, 2016 · 4 comments
Open

Time label #41

jackcarlisle opened this issue Oct 22, 2016 · 4 comments
Assignees
Labels
discuss Share your constructive thoughts on how to make progress with this issue help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue

Comments

@jackcarlisle
Copy link
Member

@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?

@jackcarlisle jackcarlisle added the question A question needs to be answered before progress can be made on this issue label Oct 22, 2016
@nelsonic
Copy link
Member

nelsonic commented Oct 22, 2016

@jackcarlisle great question! The time label e.g: T30m is added to an issue by the person who is doing the work. Initially it's a "best estimate" that the story will take 30 minutes to be "done". The label is is added before the task is started (preferably at the sprint planning stage so we can estimate a "batch" of stories before starting a sprint) so that everyone has a guide as to the perceived complexity and/or expected duration of the task/activity.

This process is designed to help us all learn how to estimate our work and get better at communicating with team members and client. ⌛️ ❓

@jackcarlisle
Copy link
Member Author

@nelsonic ok perfect thank you!

@nelsonic
Copy link
Member

nelsonic commented Oct 22, 2016

at present our time estimate/actual labels are: #10 (comment)
what should our smallest increment of time be?

At present our two most active projects have the following Time-related Labels:
cmt-time-labels

and:
oxabs-time-labels

@iteles can/should we have a T30m (one "pomodoro") label?
(yes I know, one pomodoro is 25 minutes, but I'm rounding it up because we include the "break" people should have after they finish a pomodoro...)

@iteles
Copy link
Member

iteles commented Oct 22, 2016

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 nelsonic added discuss Share your constructive thoughts on how to make progress with this issue help wanted If you can help make progress with this issue, please comment! labels Nov 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Share your constructive thoughts on how to make progress with this issue help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue
Projects
None yet
Development

No branches or pull requests

3 participants