116
edits
12%-time: Difference between revisions
Jump to navigation
Jump to search
→Doing 12%-time at Delft Solutions
| Line 19: | Line 19: | ||
## 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%-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. | ||
# Demo your work on Friday | # 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. | ## Every week on Friday in the weekly retrospective, we have an agenda item for showing the results of our 12%-time. | ||