116
edits
12%-time: Difference between revisions
Jump to navigation
Jump to search
→Doing 12%-time at Delft Solutions
| (One intermediate revision by the same user not shown) | |||
| Line 17: | Line 17: | ||
# How to budget & plan for 12%-time: | # How to budget & plan for 12%-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. As a general rule, do not go over 5 hours in a particular week. | ## 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. As a general rule, do not go over 5 hours in a particular 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 worked 5 hours on 12%-time this week, try doing 3 hours next week. | ||
## If you miss 12%-time multiple weeks in a row, bring it up as a topic for the weekly retrospective. It indicates that the workload is not correctly distributed throughout the team. If the whole team is not getting to 12%-time multiple weeks in a row, that's a strong indicator that we're overloaded. | ## If you miss 12%-time multiple weeks in a row, bring it up as a topic for the weekly retrospective. It indicates that the workload is not correctly distributed throughout the team. If the whole team is not getting to 12%-time multiple weeks in a row, that's a strong indicator that we're overloaded. | ||
## Plan your 12%-time towards the end of the workweek, probably Thursdays and Fridays, as it becomes clear that work objectives will be delivered on time for this week. 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. | ## Plan your 12%-time towards the end of the workweek, probably Thursdays and Fridays, as it becomes clear that work objectives will be delivered on time for this week. 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. | ||
| Line 24: | Line 24: | ||
## Prepare beforehand to discuss your 12%-time in the past week. In about 3-4 minutes, you should share: | ## Prepare beforehand to discuss your 12%-time in the past week. In about 3-4 minutes, you should share: | ||
### anything new you've built | ### anything new you've built | ||
### any learnings you had. | ### any learnings you had. Never assume that everyone else already knows what you've learned this week. That's almost never the case. | ||
### You can talk about your process | ### You can talk about your process or what you did, but this should not be an exhaustive summary of your time spent. Focus on the results and outcomes. | ||