116
edits
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
# How to budget time: | # How to budget time: | ||
## Limit your 12% time to 4 hours per week over a long term average. It's okay to spend more or less time on 12% time per week, it doesn't have to be exactly 4 hours. | ## Limit your 12% time to 4 hours per week over a long term average. It's okay to spend more or less time on 12% time per week, it doesn't have to be exactly 4 hours. | ||
## Missing work objectives or deadlines while still working 12% time in a particular week is a major cause for concern and should never happen! The 12% time is a buffer, not a dedicated project. It is of course possible, to consume the buffer entirely and still miss a deadline: bring it up at the retrospective if that's the case. | |||
## Try to stick closely to four hours per week though; having you do 0-0-0-16 hours in a month would defeat goal 1 of having slack every week. | ## Try to stick closely to four hours per week though; having you do 0-0-0-16 hours in a month would defeat goal 1 of having slack every week. | ||
## Do not catch-up on 'missed' 12% time. If a week was quite busy, the work consumes the 12% time as a buffer, as it was intended. The next week, just do 4 hours rather than 8 hours on 12% time. | ## Do not catch-up on 'missed' 12% time. If a week was quite busy, the work consumes the 12% time as a buffer, as it was intended. The next week, just do 4 hours rather than 8 hours on 12% time. | ||
## If you miss 12% multiple weeks in a row, especially when you do so as the whole team, bring it up as a topic for the weekly retrospective. It's an early sign that we might be overbooked w.r.t. capacity. | ## If you miss 12% multiple weeks in a row, especially when you do so as the whole team, bring it up as a topic for the weekly retrospective. It's an early sign that we might be overbooked w.r.t. capacity. | ||
# Planning when to take 12% time: | # Planning when to take 12% time: | ||
## Spend your 12% time towards the end of the workweek, probably Thursday or Friday, as it becomes clear that work objectives will be delivered on time for this week. | |||
## Do not spend 12% time on weekends to catch up on your hours for the week. Weekends should -- practically and legally -- be for rest, while 12% time is still considered work. | |||
# Demo your work on Friday | |||
## Every week on Friday in the weekly retrospective, we have an agenda item for showing the results of our 12% time. | |||
## Prepare beforehand to discuss your 12% time in the past week. In about 3-4 minutes, you should share: | |||
### anything new you've built | |||
### any learnings you had. Don't assume that everyone already knows what you've learned: often that's not the case! | |||
### You can talk about your process of going about it, but the main focus should be on results. | |||
edits