jimbojsb/gist:6424630

## gistfile1.txt
All,

In an effort to try and figure out how we can get more done, I need to collect some more data on what we're currently doing and how long it's taking. As I mentioned last week, please make sure to log work on tickets at the time the work is done, don't save it until the ticket is complete. For tickets that take >1 day, I would expect this means you're  at least logging work on them twice a day. I want to make sure the estimates and work logs on the ticket are for programming time only. Don't factor in the auxiliary tasks like code reviews or acceptance meetings in either the estimates or the work logs. If you have to go spend 2 hours learning something to get a ticket accomplished, go ahead and count that as a work log, and also include it in the estimates.


The main things i'm trying to learn are 1) how much capacity do build things do we actually have, and 2) can we get more by improving efficiency, and if not, how many people do we need to hire.  With that in mind, and looking at past weeks' number of hours logged on tickets, I'm setting the following soft goal: Each of you should be able to log a minimum of 25 hours a week of time on items in Jira. That's 5 hours a day, which I think leaves a very generous window for other things, like code reviews, estimation, meetings, etc. I realize it's easy to game this metric, so I'm trusting you not to. I will review the numbers on Friday afternoon before I leave and see how we did. If you don't actually have 25 hours of work in your queue, it's your responsibility to come to me or Dave before lunch today and get that taken care of. Note: for this week, obviously it will be 20 hours as the goal and not 25 hours, since we had Monday off.

Also, for this week and next week, please keep a personal log of time you spend on things that are not directly related to work on tickets. This includes: lunch, waiting for your site to build, code reviews, estimation, acceptance meetings, any other meetings, answering emails, discussing features with the product team, reading reddit, looking at cat videos, etc. Please send these to me by the end of the day Friday. Please be as accurate as you can, if you spend 2 hours this week watching cat videos, that's fine, I'm not judging, I just want to get a clear picture. The format is not important, whatever works for you is fine.


Thanks in advance for helping with this.
	All,

	In an effort to try and figure out how we can get more done, I need to collect some more data on what we're currently doing and how long it's taking. As I mentioned last week, please make sure to log work on tickets at the time the work is done, don't save it until the ticket is complete. For tickets that take >1 day, I would expect this means you're at least logging work on them twice a day. I want to make sure the estimates and work logs on the ticket are for programming time only. Don't factor in the auxiliary tasks like code reviews or acceptance meetings in either the estimates or the work logs. If you have to go spend 2 hours learning something to get a ticket accomplished, go ahead and count that as a work log, and also include it in the estimates.


	The main things i'm trying to learn are 1) how much capacity do build things do we actually have, and 2) can we get more by improving efficiency, and if not, how many people do we need to hire. With that in mind, and looking at past weeks' number of hours logged on tickets, I'm setting the following soft goal: Each of you should be able to log a minimum of 25 hours a week of time on items in Jira. That's 5 hours a day, which I think leaves a very generous window for other things, like code reviews, estimation, meetings, etc. I realize it's easy to game this metric, so I'm trusting you not to. I will review the numbers on Friday afternoon before I leave and see how we did. If you don't actually have 25 hours of work in your queue, it's your responsibility to come to me or Dave before lunch today and get that taken care of. Note: for this week, obviously it will be 20 hours as the goal and not 25 hours, since we had Monday off.

	Also, for this week and next week, please keep a personal log of time you spend on things that are not directly related to work on tickets. This includes: lunch, waiting for your site to build, code reviews, estimation, acceptance meetings, any other meetings, answering emails, discussing features with the product team, reading reddit, looking at cat videos, etc. Please send these to me by the end of the day Friday. Please be as accurate as you can, if you spend 2 hours this week watching cat videos, that's fine, I'm not judging, I just want to get a clear picture. The format is not important, whatever works for you is fine.


	Thanks in advance for helping with this.