12%-time - Revision history

Jakobbuis: /* Doing 12%-time at Delft Solutions */

2025-03-04T14:32:01Z

Doing 12%-time at Delft Solutions

← Older revision		Revision as of 07:32, 4 March 2025
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.

Jakobbuis: /* Doing 12%-time at Delft Solutions */

2025-03-04T14:31:03Z

Doing 12%-time at Delft Solutions

← Older revision		Revision as of 07:31, 4 March 2025
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. ~~Don't~~ assume that everyone already knows what you've learned~~: often that~~'s ~~not~~ the case!		### 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 ~~of going about it~~, but ~~the main focus~~ should be on results.		### 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.

Jakobbuis: /* Doing 12%-time at Delft Solutions */

2025-03-04T14:28:40Z

Doing 12%-time at Delft Solutions

← Older revision		Revision as of 07:28, 4 March 2025
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.
	## ~~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. 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.
	# 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.

Jakobbuis: /* Doing 12%-time at Delft Solutions */

2025-03-04T14:28:16Z

Doing 12%-time at Delft Solutions

← Older revision		Revision as of 07:28, 4 March 2025
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.
	## 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.		## 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. 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.
	## 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.

Jakobbuis: /* Doing 12%-time at Delft Solutions */

2025-03-04T14:27:56Z

Doing 12%-time at Delft Solutions

← Older revision		Revision as of 07:27, 4 March 2025
Line 18:		Line 18:
	## 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 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 ~~early~~ 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.
	## 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.		## 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.
	## 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.		## 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.

Jakobbuis: /* Doing 12%-time at Delft Solutions */

2025-03-04T14:27:31Z

Doing 12%-time at Delft Solutions

← Older revision		Revision as of 07:27, 4 March 2025
Line 18:		Line 18:
	## 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 miss 12%-time 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%-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 early indicator that we're overloaded.
	## 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.		## 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.
	## 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.		## 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.

Jakobbuis: /* Doing 12%-time at Delft Solutions */

2025-03-04T14:25:29Z

Doing 12%-time at Delft Solutions

← Older revision		Revision as of 07:25, 4 March 2025
Line 16:		Line 16:
	## What you work on, should be "work-related". We take a broad view of that requirement; it doesn't have to be directly related to your job. Learning a new programming language, trying a new technology, building a badge reader for the office door, learning bookkeeping or accounting, making a meeting timer, etc. are all great examples of using 12%-time. On the contrary, underwater basket weaving, sleeping, and remodelling your bathroom are not.		## What you work on, should be "work-related". We take a broad view of that requirement; it doesn't have to be directly related to your job. Learning a new programming language, trying a new technology, building a badge reader for the office door, learning bookkeeping or accounting, making a meeting timer, etc. are all great examples of using 12%-time. On the contrary, underwater basket weaving, sleeping, and remodelling your bathroom are not.
	# 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 miss 12%-time 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%-time 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.

Jakobbuis: /* Doing 12%-time at Delft Solutions */

2025-03-04T14:24:55Z

Doing 12%-time at Delft Solutions

← Older revision		Revision as of 07:24, 4 March 2025
Line 16:		Line 16:
	## What you work on, should be "work-related". We take a broad view of that requirement; it doesn't have to be directly related to your job. Learning a new programming language, trying a new technology, building a badge reader for the office door, learning bookkeeping or accounting, making a meeting timer, etc. are all great examples of using 12%-time. On the contrary, underwater basket weaving, sleeping, and remodelling your bathroom are not.		## What you work on, should be "work-related". We take a broad view of that requirement; it doesn't have to be directly related to your job. Learning a new programming language, trying a new technology, building a badge reader for the office door, learning bookkeeping or accounting, making a meeting timer, etc. are all great examples of using 12%-time. On the contrary, underwater basket weaving, sleeping, and remodelling your bathroom are not.
	# 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 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 miss 12%-time 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%-time 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.

Jakobbuis: /* Doing 12%-time at Delft Solutions */

2025-03-04T14:24:41Z

Doing 12%-time at Delft Solutions

← Older revision		Revision as of 07:24, 4 March 2025
Line 16:		Line 16:
	## What you work on, should be "work-related". We take a broad view of that requirement; it doesn't have to be directly related to your job. Learning a new programming language, trying a new technology, building a badge reader for the office door, learning bookkeeping or accounting, making a meeting timer, etc. are all great examples of using 12%-time. On the contrary, underwater basket weaving, sleeping, and remodelling your bathroom are not.		## What you work on, should be "work-related". We take a broad view of that requirement; it doesn't have to be directly related to your job. Learning a new programming language, trying a new technology, building a badge reader for the office door, learning bookkeeping or accounting, making a meeting timer, etc. are all great examples of using 12%-time. On the contrary, underwater basket weaving, sleeping, and remodelling your bathroom are not.
	# 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.		## 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 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%-time 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%-time 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.

Jakobbuis: /* Doing 12%-time at Delft Solutions */

2025-03-04T14:24:09Z

Doing 12%-time at Delft Solutions

← Older revision		Revision as of 07:24, 4 March 2025
Line 14:		Line 14:
	## Choose your own topics & projects. No one assigns you 12% work. While others might have suggestions, you decide how to allocate time.		## Choose your own topics & projects. No one assigns you 12% work. While others might have suggestions, you decide how to allocate time.
	## You can work on things over multiple weeks, or choose a different topic every week for variation.		## You can work on things over multiple weeks, or choose a different topic every week for variation.
	## What you work on, should be "work-related". We take a broad view of that requirement; it doesn't have to be directly related to your job. Learning a new programming language, trying ~~some~~ new technology, building a badge reader for the office door, learning bookkeeping or accounting, making a meeting timer, etc. are all great examples of using 12%-time. On the contrary, underwater basket weaving, sleeping, or remodelling your bathroom are not.		## What you work on, should be "work-related". We take a broad view of that requirement; it doesn't have to be directly related to your job. Learning a new programming language, trying a new technology, building a badge reader for the office door, learning bookkeeping or accounting, making a meeting timer, etc. are all great examples of using 12%-time. On the contrary, underwater basket weaving, sleeping, and remodelling your bathroom are not.
	# 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.		## 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.