>It seems like you could solve this problem in an even more dev-friendly way by sticking to one of the most fundamental principles in scrum (and possibly others): Don't schedule 100% of your developers' time, and definitely don't fill them up to 100% on coding work. Not even close. Devs are supposed to work at a sustainable pace.
This sounds great until you work someplace where you need to allocate 7.5 hours every day to a billable project.
If you don't allocate 7.5 hours you are asked what you were doing the rest of the day...
I've seen where someone won't have a conversation at work because they can't allocate a project to 10 mins chatting with work colleagues.
Or when you get asked a coding question from a junior and so you help them, but then need to get their project code they were working on so you can allocate that 10 minute chatting /giving advice to that project.
Or helping a junior with something they are stuck on, management sees and questions why two devs are sitting at one machine...
This sounds great until you work someplace where you need to allocate 7.5 hours every day to a billable project.
If you don't allocate 7.5 hours you are asked what you were doing the rest of the day...
I've seen where someone won't have a conversation at work because they can't allocate a project to 10 mins chatting with work colleagues.
Or when you get asked a coding question from a junior and so you help them, but then need to get their project code they were working on so you can allocate that 10 minute chatting /giving advice to that project.
Or helping a junior with something they are stuck on, management sees and questions why two devs are sitting at one machine...