116
edits
12%-time: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
== Goals == | == Goals == | ||
12% Time creates structured slack in employees' schedules. This has two primary goals: | 12% Time creates structured slack in employees' schedules. This has two primary goals: | ||
# force us to create slack in project schedules, that can be consumed when time runs over. | |||
# allow for more experimentation and creativity that might not naturally come up in projects. | |||
Slack in projects is important. A fully utilized project (or team) is virtually guaranteed to fail to meet its deadlines: any small delay during a project would cause you to violate the deadline. One of the ways we build ensure slack is included in our workweek, is by booking ''up to 4 hours'' every week of 12% time. Yes, that's actually 12,5% of your 32-hour workweek, but the shorter name has stuck. | Slack in projects is important. A fully utilized project (or team) is virtually guaranteed to fail to meet its deadlines: any small delay during a project would cause you to violate the deadline. One of the ways we build ensure slack is included in our workweek, is by booking ''up to 4 hours'' every week of 12% time. Yes, that's actually 12,5% of your 32-hour workweek, but the shorter name has stuck. | ||
| Line 11: | Line 11: | ||
== Doing 12% time at Delft Solutions == | == Doing 12% time at Delft Solutions == | ||
# What to work on: | |||
## Choose your own topics & projects. Noone assigns you 12% work. While others might have suggestions, you decide how to allocate time. | |||
## You can work on things over multiple weeks, or | |||
# 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. | |||
## 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. | |||
## 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: | |||
choose your own topic | choose your own topic | ||
do this at the end of the week, once work is done | do this at the end of the week, once work is done | ||
preferably not in the weekend | preferably not in the weekend | ||
demo your work or share learnings Friday | demo your work or share learnings Friday | ||